From a13877450350ce39395a11f27bf058c7f288d6f8 Mon Sep 17 00:00:00 2001 From: Michiel ter Reehorst Date: Mon, 26 Feb 2018 13:22:12 +0100 Subject: [PATCH] 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 https://github.com/apollographql/meteor-integration/issues/92 for discussion. --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index bbdeb34..23931cf 100644 --- 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 `this.userId` when called 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