`missionPatch`'s type in the schema must have accidentally been changed from `String` to `PatchSize` when a resolver was added.
This causes a fairly difficult to debug error in the Client UI while working through the tutorial. (at least for graphQL newbies like me)
This part of the tutorial is no longer working.
As such, it only hampers someone trying to work through the tutorial.
Even following the suggestions in https://github.com/apollographql/apollo/issues/264, I was not able to create a successful deployment. (If I had, I would have opened a PR to fix the instructions.)
Since this seems to be producing a more negative experience than positive, I suggest removing this part of the tutorial until working instructions become available.
The last paragraph of the resolvers.md file is not accurate. It states that the next section will be "...about testing your graph." However, the next section linked is "4. Run your graph in production". I would propose that the graph testing actually be put as the next section instead of how to run in production.
The first code snippet was missing the name of the file is editing. Even though the description explains which file has to be edited, the rest of the code snippets contain the path of the file to modify.
So I added it to make it more hegemony along the rest of the code snippets.
The existing documentation mentions that "_Your schema code will go inside the `gql` function,_" but I found that easy to miss and only informative in retrospect. This change adds another line immediately before the reader needs to know where the SDL code goes to help curb the confusion that I went through.
I felt like the text saying to include schema stuff "inside the gql function" may not be quite clear enough for folks who haven't seen template strings or perhaps haven't seen template strings used as a function in that style.
Initializers are no longer part of the AC local state API. We're
now recommending that people use `cache.writeData` directly, since
it's already part of the Apollo Cache API and is more flexible.
