[11.x] Use Date facade for storing the password confirmation timestamp
#54383
Conversation
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
This matches the changes via laravel/fortify#520 -------------- Currently, the password confirmation endpoint uses PHP's inbuilt `time()` function. This does not consider `freezeSecond()` or `Date::setTestNow()`. Leading to inconsistent results during tests. This update maintains compatibility with existing features as both `time()` and `->unix()` return a UNIX timestamp. Signed-off-by: Mior Muhammad Zaki <crynobone@gmail.com>
crynobone
commented
Jan 28, 2025
| @@ -6,6 +6,7 @@ | |||
| use Illuminate\Contracts\Session\Session; | |||
| use Illuminate\Support\Arr; | |||
| use Illuminate\Support\Collection; | |||
| use Illuminate\Support\Facades\Date; | |||
There was a problem hiding this comment.
This is already been used in illuminate/session so adding this should be safe.
Sign up for free
to join thi
59AF
s 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.
This matches the changes via laravel/fortify#520
Problem
Currently, the password confirmation endpoint uses PHP's inbuilt
time()function. This does not considerfreezeSecond()orDate::setTestNow(). Leading to inconsistent results during tests.Solution
This update maintains compatibility with existing features as both
time()and->unix()return a UNIX timestamp.