Graphql policies fix #4008
Merged
Graphql policies fix #4008
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ries had ctx.state.user as undefined
… key instead of 'policy'
…mposeMutationResolver() and Query.composeQueryResolver()
|
Awesome 😃 Thanks for your work @donmasakayan |
This was referenced Sep 16, 2019
alexandrebodin
changed the title
alexandrebodin
added
pr: 🐛 Bug fix
source: core:content-manager
This was referenced Mar 23, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Old deprecated PR: #3881
Description of what you did:
Fixes three issues as outlined in this issue:
fix #3880 fix #2766
Issue 1: Inaccurate Documentation on GraphQL Policies
Issue 2: Policies not triggering for custom Mutations
Issue 3: Policies don't have
ctx.state.userMy PR is a:
Main update on the:
Manual testing done on the following databases: