Release0.7 with bug fix for CosmosDB field auth when graphql is true
, include
is *
#1516
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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?