Adding configurable team resolver for permission team id #2790
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.
This adds a configurable team resolver to the permission registrar class.
This allows users to implement their own storage for the team id. This is useful if you are setting a
current_team_id
on the user table similar to how jetstream works..By implementing a resolver in this way, the middleware approach is optional as the resolver will always go through your logic via CLI, HTTP, or otherwise. Which means less explicit calls to
setPermissionsTeamId
.We are defaulting to the
DefaultTeamResolver
so that we are backwards compatible with anyone that already has the config published.Let me know if more tests are desired, I felt that the current tests did a good job covering the setting and getting of team permission id.
Example of a custom resolver:
App\Permissions\CustomerTeamResolver.php
config/permission.php