kylefang/apollo
1
0
Fork 0
mirror of https://github.com/zhigang1992/apollo.git synced 2026-01-12 08:53:57 +08:00
Code Issues Packages Projects Releases Wiki Activity

Remove unnecessary schema change

Browse Source 
Other it's very confusing on why this change is needed
This commit is contained in:
Zhigang Fang
2019-08-30 11:48:04 +08:00
committed by GitHub
parent 596d075a04
commit e3d3019c2e
1 changed files with 0 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -253,14 +253,6 @@ Mission: {
},
```
_src/schema.js_
```js
type Mission {
# ... with rest of schema
missionPatch(mission: String, size: PatchSize): String
}
```
The first argument passed into our resolver is the parent, which refers to the mission object. The second argument is the size we pass to our `missionPatch` field, which we use to determine which property on the mission object we want our field to resolve to.
Now that we know how to add resolvers on types other than `Query` and `Mission`, let's add some more resolvers to the `Launch` and `User` types. Copy this code into your resolver map: