Repository navigation
test(hydra): prove the operation filter with a permission attribute - #20
Merged
Merged
Conversation
Replace the role name in the security expression of the Hydra operation
filter test with the example permission attribute is_granted('thing:write')
and add two regression tests: for collection operations the expression
reaches the ResourceAccessChecker unchanged, with object = null, and the
checker's answer decides whether the POST operations are advertised.
README and CHANGELOG (Unreleased) state that the filter is
expression-neutral and that this bundle defines no permissions of its own.
No change under src/ or config/.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Summary
is_granted('thing:write')instead of a role name in thesecurityexpression. The repository no longer contains any role name.ResourceAccessCheckerunchanged (asserted as a string literal) withobject = null, and that the checker's answer alone decides whether the create and scanPOSToperations are advertised.nullsubject for collection operations.## Unreleasedsection.Tests and documentation only. No change under
src/,config/,composer.jsonor.github/, no behaviour change, no tag planned.Test plan
git grep ROLE_returns nothing🤖 Generated with Claude Code