Feat add parent to resolve permissions #816
Draft
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
chrisvxd
force-pushed
the
feat-add-parent-to-resolve-permissions
branch
from
b134efd to
281114d
Compare
chrisvxd
force-pushed
the
feat-add-parent-to-resolve-permissions
branch
from
281114d to
948c22a
Compare
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.
WIP for adding
parentto permission resolvers. This requires a refactor of pathData, as this is not known at the time of calculating resolvers. This will enable you to set permissions based on the parent, for example, if you wish to disable deletion of items inside a particular componentUnfortunately this is non-trivial due to the nature of DropZone remounting, and it may be better to wait for the slots API which won't require remounting.