You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe
Currently, one has to write the schema rule without any intellisense for the schema types. With bigger schema, it can be easy to forget writting rules for specific fields, mutation or query.
Describe the solution you'd like
The possibility to generate a fully typed permission schema based on the user's graphql schema using graphql-codegen.
Describe alternatives you've considered
The way I currently implement is using deny as a fallback rule and implement the rules for the schema from there. Unfortunately It is easy to forget some part of the schema and find out only when testing.
The text was updated successfully, but these errors were encountered:
Feature request
Is your feature request related to a problem? Please describe
Currently, one has to write the schema rule without any intellisense for the schema types. With bigger schema, it can be easy to forget writting rules for specific fields, mutation or query.
Describe the solution you'd like
The possibility to generate a fully typed permission schema based on the user's graphql schema using graphql-codegen.
Describe alternatives you've considered
The way I currently implement is using deny as a fallback rule and implement the rules for the schema from there. Unfortunately It is easy to forget some part of the schema and find out only when testing.
The text was updated successfully, but these errors were encountered: