Merge branch 'source' into source

Author: gregology

site/_core/HeaderLinks.js

@@ -12,8 +12,8 @@ const links = [
   { section: 'learn', text: 'Learn', href: '/learn/' },
   { section: 'code', text: 'Code', href: '/code/' },
   { section: 'community', text: 'Community', href: '/community/' },
-  { section: 'blog', text: 'Blog', href: '/blog/' },
-  { section: 'spec', text: 'Spec', href: 'http://facebook.github.io/graphql/' },
+  { section: 'spec', text: 'Spec', href: 'https://facebook.github.io/graphql/' },
+  { section: 'foundation', text: 'Foundation', href: 'https://foundation.graphql.org/' },
 ];
 
 export default ({ section }) =>

site/_core/Site.js

@@ -81,9 +81,9 @@ export default ({ page, category, title, section, className, noSearch, children
           </div>
           <div>
             <h5>More</h5>
-            <a href="/blog">GraphQL Team Blog</a>
-            <a href="http://facebook.github.io/graphql/" target="_blank" rel="noopener noreferrer">Read the Spec</a>
-            <a href="https://github.com/graphql" target="_blank" rel="noopener noreferrer">GitHub</a>
+            <a href="https://facebook.github.io/graphql/" target="_blank" rel="noopener noreferrer">GraphQL Specification</a>
+            <a href="https://foundation.graphql.org/" target="_blank" rel="noopener noreferrer">GraphQL Foundation</a>
+            <a href="https://github.com/graphql" target="_blank" rel="noopener noreferrer">GraphQL GitHub</a>
             {page && <a href={'https://github.com/graphql/graphql.github.io/edit/source/site/' + page.relPath} target="_blank" rel="noopener noreferrer">Edit this page &#x270E;</a>}
           </div>
         </section>

site/blog/20160502-rest-api-graphql-wrapper.md

@@ -141,7 +141,7 @@ const PersonType = new GraphQLObjectType({
     /* ... */
     friends: {
       type: new GraphQLList(PersonType),
-      resolve: person => person.friends.map(getPersonByURL),
+      resolve: person => person.friends.map(fetchPersonByURL),
     },
   }),
 });
@@ -395,7 +395,7 @@ To create a `DataLoader` you supply a method that can resolve a list of objects
 
 ```js
 const personLoader = new DataLoader(
-  urls => Promise.all(urls.map(getPersonByURL))
+  urls => Promise.all(urls.map(fetchPersonByURL))
 );
 ```
 

site/code/index.html.js

@@ -42,7 +42,7 @@ In addition to the GraphQL [reference implementations in JavaScript](#javascript
 
   - [graphql-dotnet](https://github.com/graphql-dotnet/graphql-dotnet): GraphQL for .NET
   - [graphql-net](https://github.com/ckimes89/graphql-net): Convert GraphQL to IQueryable
-  - [Hot Chocolate](https://github.com/ChilliCream/hotchocolate): GraphQL Service for .net core and .net classic
+  - [Hot Chocolate](https://github.com/ChilliCream/hotchocolate): GraphQL Server for .net core and .net classic
 
 ### Clojure
 
@@ -107,7 +107,9 @@ Code that executes a hello world GraphQL query with \`graphql-clj\`:
 (executor/execute nil schema resolver-fn "{ hello }")
 \`\`\`
 
-  - [lacinia](https://github.com/walmartlabs/lacinia): A full implementation of the GraphQL specification that aims to maintain external compliance with the specification.
+#### [lacinia](https://github.com/walmartlabs/lacinia)
+
+A full implementation of the GraphQL specification that aims to maintain external compliance with the specification.
 
 ### Elixir
 
@@ -121,8 +123,9 @@ Code that executes a hello world GraphQL query with \`graphql-clj\`:
 ### Go
 
   - [graphql-go](https://github.com/graphql-go/graphql): An implementation of GraphQL for Go / Golang.
+  - [graph-gophers/graphql-go](https://github.com/graph-gophers/graphql-go): An active implementation of GraphQL in Golang (was https://github.com/neelance/graphql-go).
+  - [GQLGen](https://github.com/99designs/gqlgen) - Go generate based graphql server library.
   - [graphql-relay-go](https://github.com/graphql-go/relay): A Go/Golang library to help construct a graphql-go server supporting react-relay.
-  - [neelance/graphql-go](https://github.com/neelance/graphql-go): An active implementation of GraphQL in Golang.
   - [machinebox/graphql](https://github.com/machinebox/graphql): An elegant low-level HTTP client for GraphQL.
   - [samsarahq/thunder](https://github.com/samsarahq/thunder): A GraphQL implementation with easy schema building, live queries, and batching.
 
@@ -334,7 +337,8 @@ $resolvers = [
 ];
 $schema = Graphql\schema($typeDefs, $resolvers);
 
-echo "Server running at http://127.0.0.1:8080\n";
+echo "Server running at http://127.0.0.1:8080";
+
 Http\server(Graphql\psr7($schema), function (\Throwable $err) {
     var_dump($err);
     return Diactoros\json([
@@ -471,6 +475,7 @@ Executor.execute(schema, query) map println
   - [nanogql](https://github.com/yoshuawuyts/nanogql): Tiny GraphQL client library using template strings.
   - [gq-loader](https://github.com/Houfeng/gq-loader): A simple JavaScript GraphQL client，Let the *.gql file be used as a module through webpack loader.
   - [AWS Amplify](https://aws.github.io/aws-amplify): A JavaScript library for application development using cloud services, which supports GraphQL backend and React components for working with GraphQL data.
+  - [Grafoo](https://github.com/grafoojs/grafoo): An all purpose GraphQL client with view layer integrations for multiple frameworks in just 1.6kb.
 
 ### Swift / Objective-C iOS
 

site/community/Community-Events.md

@@ -8,21 +8,21 @@ sublinks: Upcoming Events,Meetups
 
 ## Upcoming Events
 
-### GraphQL Europe Conference
+### GraphQL Summit
 
-- **Date:** June 15, 2018
-- **Location:** Berlin, Germany
-- **Link:** https://graphql-europe.org
+- **Date:** November 7-8, 2018
+- **Location:** San Francisco, U.S.A.
+- **Link:** https://summit.graphql.com
 
-GraphQL Europe is a non-profit GraphQL conference in Europe with speakers from all around the world. Learn about GraphQL best practices from industry experts and become part of the thriving GraphQL community. 
+World's largest conference dedicated to GraphQL.
 
-### GraphQL Finland Conference
+### GraphQL Conf Berlin 2019
 
-- **Date:** October 18-19, 2018
-- **Location:** Helsinki, Finland
-- **Link:** https://graphql-finland.fi/
+- **Date:** June 20-21, 2019
+- **Location:** Berlin, Germany
+- **Link:** https://www.graphqlconf.org/
 
-GraphQL Finland is a community-organized GraphQL conference. The first of its kind in Finland, the event consists of a workshop day and a day of talks around the topic. GraphQL Finland is organized by the same team that brought you React Finland.
+GraphQL Conf is a non-profit GraphQL conference in Europe with speakers from all around the world. Learn about GraphQL best practices from industry experts and become part of the thriving GraphQL community. 
 
 ## Meetups
 
@@ -72,3 +72,4 @@ GraphQL Finland is a community-organized GraphQL conference. The first of its ki
 - [GraphQL Tel Aviv](https://www.meetup.com/GraphQL-TLV/)
 - [GraphQL Tokyo](https://www.meetup.com/GraphQL-Tokyo/)
 - [GraphQL Meetup (Bangalore)](https://www.meetup.com/GraphQL-Meetup/)
+- [GraphQL Meetup (Bangkok)](https://www.meetup.com/GraphQL-Bangkok/)

site/community/Community-Resources.md

@@ -22,7 +22,6 @@ Use the [**#graphql** hashtag](https://twitter.com/search?q=%23GraphQL&src=tyah)
 Here are some helpful accounts to follow:
 - [@GraphQL](https://twitter.com/GraphQL)
 - [@graphqlweekly](https://twitter.com/graphqlweekly)
-- [@graphqlnews](https://twitter.com/graphqlnews)
 - [@GraphQLStackOverflow](https://twitter.com/GraphQLatSO)
 - [@apollographql](https://twitter.com/apollographql)
 - [@graphcool](https://twitter.com/graphcool)
@@ -51,13 +50,19 @@ Join #graphql on the [ReactiFlux Discord](http://join.reactiflux.com/).
 
 Here are a list of notable blog posts to help you better understand GraphQL:
 
+- [GraphQL: A data query language](/blog/graphql-a-query-language/) - Lee Byron
+- [Subscriptions in GraphQL and Relay](/blog/subscriptions-in-graphql-and-relay/) - Dan Schafer and Laney Kuenzel
+- [Mocking your server is easy with GraphQL](/blog/mocking-with-graphql/) - Jonas Helfer
+- [Wrapping a REST API in GraphQL](/blog/rest-api-graphql-wrapper/) - Steven Luscher
+- [Leaving technical preview](/blog/production-ready/) - Lee Byron
+- [Relicensing the GraphQL specification](https://medium.com/@leeb/relicensing-the-graphql-specification-e7d07a52301b) - Lee Byron
 - [GraphQL Introduction](https://facebook.github.io/react/blog/2015/05/01/graphql-introduction.html) - Nick Schrock
 - [From REST to GraphQL](https://0x2a.sh/from-rest-to-graphql-b4e95e94c26b#.tag7nzkrb) - Jacob Gillespie
 - [GraphQL Explained](https://medium.com/apollo-stack/graphql-explained-5844742f195e#.zdykxos6i) - Jonas Helfer
 - [GraphQL Concepts Visualized](https://medium.com/apollo-stack/the-concepts-of-graphql-bc68bd819be3#.hfczgtdsj) - Dhaivat Pandya
 - [Building the f8 App: Using GraphQL & Relay](http://makeitopen.com/docs/en/1-A2-relay.html)
 - [Your First GraphQL Server](https://medium.com/the-graphqlhub/your-first-graphql-server-3c766ab4f0a2#.ovn0y19k4) - Clay Allsopp
-- [Tutorial: Kick start a JS API with Apollo-server, Dataloader and Knex](https://bamtech.gitbooks.io/dev-standards/content/backend/graphql-js/getting-started-with-apollo-server-dataloader-knex.mo.html) - Thomas Pucci
+- [Tutorial: Kick start a JS API with Apollo-server, Dataloader and Knex](https://bamtech.gitbook.io/dev-standards/backend/graphql-js/getting-started-with-apollo-server-dataloader-knex.mo) - Thomas Pucci
 - [Tutorial: How to Build a GraphQL Server](https://medium.com/apollo-stack/tutorial-building-a-graphql-server-cddaa023c035#.bu6sdnst4) - Jonas Helfer
 - [Designing Powerful APIs with GraphQL Query Parameters](https://www.graph.cool/docs/tutorials/designing-powerful-apis-with-graphql-query-parameters-aing7uech3/) - Johannes Schickling
 - [GraphQL and the amazing Apollo Client](https://medium.com/google-developer-experts/graphql-and-the-amazing-apollo-client-fe57e162a70c) - Gerard Sans

site/google437284cc1356bc93.html.txt

@@ -0,0 +1 @@
+google-site-verification: google437284cc1356bc93.html

site/graphql-js/APIReference-Language.md

@@ -196,7 +196,7 @@ function visit(root, visitor, keyMap)
 
 visit() will walk through an AST using a depth first traversal, calling
 the visitor's enter function at each node in the traversal, and calling the
-leave function after visiting that node and all of it's child nodes.
+leave function after visiting that node and all of its child nodes.
 
 By returning different values from the enter and leave functions, the
 behavior of the visitor can be altered, including skipping over a sub-tree of

site/learn/BestPractice-Introduction.md

@@ -16,7 +16,7 @@ Following are brief descriptions of some of the more common best practices and o
 
 ### HTTP
 
-GraphQL is typically served over HTTP via a single endpoint which expresses the full set of capabilities of the service. This is in contrast to REST APIs which expose a suite of URLs each of which expose a single resource. While GraphQL could be used alongside a suite of resource URLs, this can make it harder to use with tools like GraphiQL.
+GraphQL is typically served over HTTP via a single endpoint which expresses the full set of capabilities of the service. This is in contrast to REST APIs which expose a suite of URLs each of which expose a single resource. While GraphQL could be used alongside a suite of resource URLs, this can make it harder to use with tools like [GraphiQL](https://github.com/graphql/graphiql).
 
 Read more about this in [Serving over HTTP](/learn/serving-over-http/).
 
@@ -40,12 +40,12 @@ While there's nothing that prevents a GraphQL service from being versioned just
 
 Why do most APIs version? When there's limited control over the data that's returned from an API endpoint, *any change* can be considered a breaking change, and breaking changes require a new version. If adding new features to an API requires a new version, then a tradeoff emerges between releasing often and having many incremental versions versus the understandability and maintainability of the API.
 
-In contrast, GraphQL only returns the data that's explicitly requested, so new capabilities can be added via new types and new fields on those types without creating a breaking change. This has lead to a common practice of always avoiding breaking changes and serving a versionless API.
+In contrast, GraphQL only returns the data that's explicitly requested, so new capabilities can be added via new types and new fields on those types without creating a breaking change. This has led to a common practice of always avoiding breaking changes and serving a versionless API.
 
 
 ### Nullability
 
-Most type systems which recognise "null" provide both the common type, and the *nullable* version of that type, where by default types do not include "null" unless explicitly declared. However in a GraphQL type system, every field is *nullable* by default. This is because there are many things which can go awry in a networked service backed by databases and other services. A database could go down, an asynchronous action could fail, an exception could be thrown. Beyond simply system failures, authorization can often be granular, where individual fields within a request can have different authorization rules.
+Most type systems which recognise "null" provide both the common type, and the *nullable* version of that type, whereby default types do not include "null" unless explicitly declared. However in a GraphQL type system, every field is *nullable* by default. This is because there are many things which can go awry in a networked service backed by databases and other services. A database could go down, an asynchronous action could fail, an exception could be thrown. Beyond simply system failures, authorization can often be granular, where individual fields within a request can have different authorization rules.
 
 By defaulting every field to *nullable*, any of these reasons may result in just that field returned "null" rather than having a complete failure for the request. Instead, GraphQL provides [non-null](/learn/schema/#lists-and-non-null) variants of types which make a guarantee to clients that if requested, the field will never return "null". Instead, if an error occurs, the previous parent field will be "null" instead.
 

site/learn/Learn-Execution.md

@@ -73,7 +73,7 @@ This example is written in JavaScript, however GraphQL servers can be built in [
 - `obj` The previous object, which for a field on the root Query type is often not used.
 - `args` The arguments provided to the field in the GraphQL query.
 - `context` A value which is provided to every resolver and holds important contextual information like the currently logged in user, or access to a database.
-- `info` A value which holds field-specific information relevant to the current query as well as the schema details, also [refer type GraphQLResolveInfo for more details](/graphql-js/type/#graphqlobjecttype).
+- `info` A value which holds field-specific information relevant to the current query as well as the schema details, also refer to [type GraphQLResolveInfo for more details](/graphql-js/type/#graphqlobjecttype).
 
 ## Asynchronous resolvers
 

site/learn/Learn-Queries.md

@@ -124,6 +124,34 @@ fragment comparisonFields on Character {
 
 You can see how the above query would be pretty repetitive if the fields were repeated. The concept of fragments is frequently used to split complicated application data requirements into smaller chunks, especially when you need to combine lots of UI components with different fragments into one initial data fetch.
 
+### Using variables inside fragments
+
+It is possible for fragments to access variables declared in the query or mutation. See [variables](#variables).
+
+```graphql
+# { "graphiql": true }
+query HeroComparison($first: Int = 3) {
+  leftComparison: hero(episode: EMPIRE) {
+    ...comparisonFields
+  }
+  rightComparison: hero(episode: JEDI) {
+    ...comparisonFields
+  }
+}
+
+fragment comparisonFields on Character {
+  name
+  friendsConnection(first: $first) {
+    totalCount
+    edges {
+      node {
+        name
+      }
+    }
+  }
+}
+```
+
 ## Operation name
 
 Up until now, we have been using a shorthand syntax where we omit both the `query` keyword and the query name, but in production apps it's useful to use these to make our code less ambiguous.

site/learn/Learn-Schema.md

@@ -42,7 +42,7 @@ The most basic components of a GraphQL schema are object types, which just repre
 ```graphql
 type Character {
   name: String!
-  appearsIn: [Episode]!
+  appearsIn: [Episode!]!
 }
 ```
 
@@ -52,7 +52,7 @@ The language is pretty readable, but let's go over it so that we can have a shar
 - `name` and `appearsIn` are _fields_ on the `Character` type. That means that `name` and `appearsIn` are the only fields that can appear in any part of a GraphQL query that operates on the `Character` type.
 - `String` is one of the built-in _scalar_ types - these are types that resolve to a single scalar object, and can't have sub-selections in the query. We'll go over scalar types more later.
 - `String!` means that the field is _non-nullable_, meaning that the GraphQL service promises to always give you a value when you query this field. In the type language, we'll represent those with an exclamation mark.
-- `[Episode]!` represents an _array_ of `Episode` objects. Since it is also _non-nullable_, you can always expect an array (with zero or more items) when you query the `appearsIn` field.
+- `[Episode!]!` represents an _array_ of `Episode` objects. Since it is also _non-nullable_, you can always expect an array (with zero or more items) when you query the `appearsIn` field. And since `Episode!` is also _non-nullable_, you can always expect every item of the array to be an `Episode` object.
 
 Now you know what a GraphQL object type looks like, and how to read the basics of the GraphQL type language.
 

site/users/index.html.js

@@ -656,6 +656,16 @@ var logos = [
     img: 'uctrends.png',
     link: 'https://trends.ucweb.com'
   },
+  {
+    name: 'Expert360',
+    img: 'expert360.png',
+    link: 'https://expert360.com'
+  },
+  {
+    name: 'Cloverleaf',
+    img: 'cloverleaf.png',
+    link: 'https://cloverleaf.me/'
+  },
   {
     name: 'Memair',
     img: 'memair.png',