-
Notifications
You must be signed in to change notification settings - Fork 162
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix Deprecation Notice in RefreshTokenAuthenticator::start Method #389
Open
gzim324
wants to merge
2
commits into
markitosgv:master
Choose a base branch
from
gzim324:refactor/nullable-types
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
Explicitly marked parameter as nullable in the start method of the RefreshTokenAuthenticator class to comply with PHP 8.1+ standards.
mbabker
approved these changes
Dec 3, 2024
maxhelias
approved these changes
Dec 3, 2024
metalmumu
approved these changes
Jan 7, 2025
muriel-hublo
approved these changes
Jan 7, 2025
@gzim324 here is the same issue, please check it as well |
This was referenced Jan 11, 2025
- Update the type hint of the parameter in the start method from AuthenticationException to ?AuthenticationException. - Enhance code clarity and ensure consistency with nullable parameter type definition.
okorneliuk
reviewed
Jan 15, 2025
@@ -178,7 +178,7 @@ public function onAuthenticationFailure(Request $request, AuthenticationExceptio | |||
return $this->failureHandler->onAuthenticationFailure($request, $exception); | |||
} | |||
|
|||
public function start(Request $request, AuthenticationException $authException = null): Response | |||
public function start(Request $request, ?AuthenticationException $authException = null): Response |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
SebLevDev
approved these changes
Jan 24, 2025
karpilin
approved these changes
Jan 31, 2025
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.
Fix Deprecation Notice in RefreshTokenAuthenticator::start Method
Summary
This pull request addresses a deprecation notice in the
GesdinetJWTRefreshTokenBundle
caused by thestart
method in theRefreshTokenAuthenticator
class. The$authException
parameter was implicitly nullable, which is deprecated in PHP 8.1+.Changes Made
start
method inRefreshTokenAuthenticator
to explicitly declare the$authException
parameter as nullable.Environment
Additional Context
This change ensures compatibility with PHP 8.1+ and eliminates the deprecation notice in development and test environments.