Fix custom permissions namespace safety #181
Open
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
MetadataTriggerHandler
andFinalizerHandler
.gitignore
to prevent Claude-related files from being committedChanges Made
checkPermissionNamespaceAware()
method to both handler classespopulatePermissionMap()
to use the new namespace-aware methodTechnical Details
When the framework is packaged in a namespace,
FeatureManagement.checkPermission()
only works for custom permissions that share the same namespace as the calling code. This fix implements a fallback mechanism that tries both the original permission name and the permission name without the namespace prefix.Test plan
Resolves #153
🤖 Generated with Claude Code