Headless CMS Security - Bring Back Old Permissions Checking-related Utils #3904
Conversation
This file contains hidden or 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
This is in order to preserve backwards compatibility.
adrians5j
changed the title
Pavel910
approved these changes
Feb 27, 2024
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.
Changes
Despite the fact that, with the #3865 PR, we've introduced the new
AccessControlclass that users can now use to perform authorization in custom CMS-related GraphQL queries/mutations, we still need to leave the old authorization/permissions utils, in order to preserve backwards compatibility.This PR brings back those utils. We'll remove them again with the 5.40.0 release.
How Has This Been Tested?
Jest.
Documentation
N/A