Should permissions.conditions apply to associations?#90
Open
charlie-s wants to merge 2 commits intoalmost-full-stack:developfrom
Open
Should permissions.conditions apply to associations?#90charlie-s wants to merge 2 commits intoalmost-full-stack:developfrom
charlie-s wants to merge 2 commits intoalmost-full-stack:developfrom
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
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.
Given these rules:
and this Graphql query:
when the Roles association is loaded, the generated SQL includes
where Role.tenantId = X, which of course doesn't exist on that model.It could be as simple as adding the
!isAssociationcheck like in this PR, but should it be going a step further and looking for any conditions defined inpermissions.rulesfor the associated model?For example, if you had
you'd probably want this condition to run as well.