Hi, When using slash graphql automatically crud resolvers are exposed. Sometimes I don’t want to expose all resolvers and let users of the API to only be able to make read-only requests for a certain type for example. I know that it is possible to guard an endpoint with @auth directive but there …

Generate Directive feature to expose only specific resolvers has been merged into master, Feat(GraphQL): Add generate directive to graphql schema by vmrajas · Pull Request #6760 · dgraph-io/dgraph · GitHub . We will soon add related documentation.

[image] spinelsun: Sometimes I don’t want to expose all resolvers and let users of the API to only be able to make read-only requests for a certain type for example. For this, I guess GraphQL can provide a Schema directive for types like: type User @CRUD(get: true, query: true, add: false, u…

@abhimanyusinghgaur , nice idea [image] abhimanyusinghgaur: type User @CRUD(get: true, query: true, add: false, update: false, delete: false) That looks familiar: [image] Mark fields / types / interfaces and skip GrapQL CRUD generation GraphQL @generate( add: Boo…

@abhimanyusinghgaur maybe for fields, you can add @readonly/@hidden or something like that

Marking this as accepted. We’ll tackle it as part of the next sprint.

if you can add support for the hidden fields it will be great too example: type User{ email: String! @hidden(unless: $isAuthenticated: "True") username: string @id ... } or type User{ email: String! @hidden(if: $isAuthenticated: “False”) username: String! @search(by: [hash]) @id …

[image] spinelsun: if you can add support for the hidden fields it will be great too Seems like you want to hide certain fields based on a value in the JWT custom claims. Is that right? What’s the use-case that you hope to be supported by this?

An example from Github - If your are an unauthenticated user you can watch other users profiles but you can’t watch their email. Other usecases might be data that is visible only for users with a specific role. Example for that might be a patien and a doctor - the doctore can have access to the pati…

Merging @CRUD and @withSubscription directive Currently, there exists a @withSubscription directive to specify whether to generate subscriptions for types or not. The current discuss post is about having a @CRUD directive to specify whether to generate get, query, add, update and delete APIs for typ…

Documentation can be found at https://dgraph.io/docs/master/graphql/schema/generate . This would be part of the 20.11 release.

Expose only specific resolvers

Issues GraphQL

amaster507 (Anthony Master) September 22, 2020, 9:54pm 4

@abhimanyusinghgaur, nice idea

That looks familiar:

Custom Mutations - Graphql

Topic		Replies	Views
Mark fields / types / interfaces and skip GrapQL CRUD generation GraphQL	7	1846	March 22, 2021
Restrict visibility of graphql mutation and queries GraphQL	4	1019	July 30, 2020
Custom Mutations - Graphql Documentation	5	959	October 12, 2020
Using @auth on individual fields? GraphQL auth , status:accepted , kind:feature	19	2878	December 2, 2021
Can i customize the graphql api in future? Dgraph	3	542	January 2, 2020

Expose only specific resolvers

Related topics