[6.x] Remove custom craft authentication guard, provider and broker#19104
Draft
riasvdv wants to merge 7 commits into
Draft
[6.x] Remove custom craft authentication guard, provider and broker#19104riasvdv wants to merge 7 commits into
riasvdv wants to merge 7 commits into
Conversation
Remove test for rendering public blade templates.
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.
Description
Now that we use and expect an eloquent model for authentication, we don't really need to provide our own guard, user provider and password broker.
Additionally this changes over usage from
Auth::craftUser()to acurrentUser()helper method. Relying on a macro on a specific guard class (SessionGuard) is brittle as for example Sanctum and Passport provide their own guard implementations.