Skip to content
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

Use Date facade for storing the password confirmation timestamp #520

Merged

Conversation

chrisvanlier2005
Copy link
Contributor

Problem

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.

Compatibility

This update maintains compatibility with existing features as both time() and ->unix() return a UNIX timestamp.

@taylorotwell taylorotwell merged commit ab1a769 into laravel:1.x Feb 8, 2024
9 checks passed
crynobone added a commit to laravel/framework that referenced this pull request Jan 28, 2025
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 pushed a commit to laravel/framework that referenced this pull request Jan 28, 2025
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>
taylorotwell pushed a commit to laravel/framework that referenced this pull request Jan 28, 2025
…amp (#54383)

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>
Co-authored-by: Chris van Lier <93382176+chrisvanlier2005@users.noreply.github.com>
taylorotwell pushed a commit to illuminate/session that referenced this pull request Jan 28, 2025
…amp (#54383)

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>
Co-authored-by: Chris van Lier <93382176+chrisvanlier2005@users.noreply.github.com>
taylorotwell pushed a commit to illuminate/support that referenced this pull request Jan 28, 2025
…amp (#54383)

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>
Co-authored-by: Chris van Lier <93382176+chrisvanlier2005@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants