Repository navigation
Use policy for viewing form entries when app registers one - #63
Merged
Merged
Conversation
When the app registers a policy for FilamentFormUser with a view() method,
use $user->can('view', $entry) instead of only allowing the submitter.
Falls back to submitter-only when no policy is present.
Made-with: Cursor
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
1 participant
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
When the consuming app registers a policy for
FilamentFormUserwith aview()method,ShowEntryuses$user->can('view', $entry)instead of only allowing the submitter. Falls back to submitter-only when no policy is present.Behavior
user_idnull): still require valid signed URL.policy($entry)hasviewmethod → use that; else only allow owner.Allows apps to grant e.g. admins permission to view any form entry via
FilamentFormUserPolicy::view().Made with Cursor