-
Notifications
You must be signed in to change notification settings - Fork 218
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
Fix issue when graphql is true and include permission is WILDCARD #1501
Conversation
I feel like #1402 will tackle this as it is more aggressive in the way that it sets the singular name, resulting in the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks for the fix and testing all other scenarios!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, Thanks @tarazou9 for addressing the change quickly.
## Why make this change? - This is for cherry-pick the bug fix from main into the release 0.7 ## What is this change? Here is the PR merged in main for the fix. #1501
Why make this change?
graphql
is set to true without singular type specified in runtime config file, in addition to when field authinclude
permission is using WILDCARD, this was giving user's access forbidden error.What is this change?
GraphQLSingularTypeToEntityNameMap
inRuntimeConfig.cs
is not adding the entity type when there is no singular type passed in, and for WILDCARD permission check, theAuthorizationResolver
is retrieving all the fields columns using theGraphQLSingularTypeToEntityNameMap
keys.How was this tested?