Fix missing LegacyPasswordAuthenticatedUserInterface #8
Conversation
This file contains 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
Rafikooo
approved these changes
Dec 12, 2022
NoResponseMate
approved these changes
Dec 12, 2022
coldic3
force-pushed
the
fix/user-salt-interface
branch
from
b25211c to
6d82669
Compare
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.
I would like to take advantage of
LegacyPasswordAuthenticatedUserInterfacewhich specifiesgetSaltmethod with?stringreturn type. The existence of this interface is checked in Symfony in some places so if the interface exists, the salt will be used back 💃