fix(jest-fake-timers): Return real Date.now() from jest.now() when real timers are in use
#13246
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
SimenB
approved these changes
Sep 10, 2022
Comment on lines
-409
to
+417
| // @ts-expect-error: condition always returns 'true' | ||
| if (this._global.setTimeout !== this._fakeTimerAPIs?.setTimeout) { | ||
| if (!this._fakingTime) { |
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
Quick follow up to #13244, applying the review suggestion that
jest.now()should return realDate.now()if real timers are in use. Currently, it will throw if the clock has not previously been initialised.Test plan
Added unit tests for the real timer case - also cleared up some
globalpollution in adjacent tests.