Skip to content
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

Merged
merged 9 commits into from
May 24, 2023

Conversation

tarazou9
Copy link
Contributor

Why make this change?

What is this change?

  • Reason for causing this is because GraphQLSingularTypeToEntityNameMap in RuntimeConfig.cs is not adding the entity type when there is no singular type passed in, and for WILDCARD permission check, the AuthorizationResolver is retrieving all the fields columns using the GraphQLSingularTypeToEntityNameMap keys.

How was this tested?

  • Integration Tests

@aaronpowell
Copy link
Contributor

I feel like #1402 will tackle this as it is more aggressive in the way that it sets the singular name, resulting in the RuntimeConfig always having a defined singular name, rather than having to rely on additional mapping data structures.

Copy link
Contributor

@Aniruddh25 Aniruddh25 left a 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!

Copy link
Contributor

@abhishekkumams abhishekkumams left a 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.

@tarazou9 tarazou9 enabled auto-merge (squash) May 24, 2023 13:55
@tarazou9 tarazou9 merged commit 5686386 into main May 24, 2023
@tarazou9 tarazou9 deleted the usrs/tarazou/fieldAuthNoSingularType branch May 24, 2023 14:20
tarazou9 added a commit that referenced this pull request May 24, 2023
## 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Getting Access forbidden message when trying to use filter on graphql queries
6 participants