kylefang/apollo
1
0
Fork 0
mirror of https://github.com/zhigang1992/apollo.git synced 2026-05-22 15:25:39 +08:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'master' into patch-1

Browse Source
This commit is contained in:
sammy
2018-12-03 18:53:44 +01:00
committed by GitHub
parent f62774bcba 8eb8fbc756
commit b45384811c
27 changed files with 1020 additions and 1451 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/source/tutorial/production.md
View File

@@ -30,7 +30,7 @@ Our key is now stored under the environment variable `ENGINE_API_KEY`.
It's time to publish our schema to Engine! First, start your server in one terminal window by running `npm start`. In another terminal window, run:
```bash
npx apollo schema:check && npx apollo schema:publish
npx apollo service:check && npx apollo service:push
```
> npx is a tool bundled with npm for easily running packages that are not installed globally.
@@ -60,4 +60,4 @@ $ npx now
The `now` command immediately deploys our graph API to the cloud and returns the hosted URL. Make sure you either copy the URL or run `npx now ls` in your terminal to retrieve the URL, since we'll need it in the following section when we build our client.
Congrats on deploying your first Apollo graph API! 🚀 Let's move on to the second half of the tutorial where we connect the API we just built to a React app.
Congrats on deploying your first Apollo graph API! 🚀 Let's move on to the second half of the tutorial where we connect the API we just built to a React app.

2
docs/source/tutorial/resolvers.md
View File

@@ -15,7 +15,7 @@ Before we can start writing resolvers, we need to learn more about what a resolv
fieldName: (parent, args, context, info) => data
```
* **root**: An object that contains the result returned from the resolver on the parent type
* **parent**: An object that contains the result returned from the resolver on the parent type
* **args**: An object that contains the arguments passed to the field
* **context**: An object shared by all resolvers in a GraphQL operation. We use the context to contain per-request state such as authentication information and access our data sources.
* **info**: Information about the execution state of the operation which should only be used in advanced cases