Skip to content

Commit b58971f

Browse files
olizillaSashko Stubailo
authored and
Sashko Stubailo
committed
Missing the (graphql#168)
1 parent cfa714c commit b58971f

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

site/learn/BestPractice-Authorization.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,6 +53,6 @@ var postType = new GraphQLObjectType({
5353
});
5454
```
5555

56-
In the example above, we see that the business logic layer requires the caller to provide a user object. If you are using GraphQL.js, the User object should be populated on the `context` argument or `rootValue` in fourth argument of the resolver.
56+
In the example above, we see that the business logic layer requires the caller to provide a user object. If you are using GraphQL.js, the User object should be populated on the `context` argument or `rootValue` in the fourth argument of the resolver.
5757

5858
We recommend passing a fully-hydrated User object instead of an opaque token or API key to your business logic layer. This way, we can handle the distinct concerns of [authentication](/graphql-js/authentication-and-express-middleware/) and authorization in different stages of the request processing pipeline.

0 commit comments

Comments
 (0)