docs: mention userId availability in method calls

And also collection hooks and other places people expect a userId. This is very important for Meteor developers, especially when using the default mongo and accounts packages. See apollographql/meteor-integration#92 for discussion.
Swydo · Feb 26, 2018 · 52cbab8 · 52cbab8
1 parent 121ae7a
commit 52cbab8
Showing 1 changed file with 1 addition and 0 deletions.
diff --git a/README.md b/README.md
@@ -3,6 +3,7 @@ DDP-Apollo has been created to leverage the power of DDP for GraphQL queries and
 
 - DDP-Apollo is one of the easiest ways to get GraphQL running for Meteor developers
 - Works with the Meteor accounts packages out of the box, giving a userId in your resolvers
+- Method calls and collection hooks will have a userId within your resolvers
 - Doesn’t require an HTTP server to be setup, like with express, koa or hapi
 - Supports GraphQL Subscriptions out-of-the-box
 - Doesn’t require an extra websocket for GraphQL Subscriptions, because DDP already has a websocket