-
-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recommended way of combining rules #733
Comments
So the current work around it to use lodash merge, it works good enough for us but it will not detect duplicate rules. Maybe a util in the library would be useful? @maticzav |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Thank you for your patience with this question. My thinking is that if you can already do that with other libraries, we don't need new functions per se. If, however, we figure out that there are potential features that can't be achieved without specific "internal" function, we should create a new one. |
Yeah external is fine I guess. |
Question about GraphQL Shield
Our schema is split between multiple typeDefs files and we use a lot of type extensions. I would like to keep the permissions near that. Either inside a resolver extension (similar to #152, but using ardatan/graphql-tools#1279 and graphql/graphql-js#1527) or as a separate file beside the typeDefs.
My problem is that we need to combine that in some way after it. What is the recommended way to do that?
Thanks!
The text was updated successfully, but these errors were encountered: