-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
runTimersToTime is badly named/not clear from docs #4723
Comments
We can start by clarifying the docs. Could you send a PR for that? |
I'd be happy to put in a PR for the docs. If the behaviour is going to stay the same, would it be useful to add an alias for this function, with a view to renaming it in future? |
I agree the name is not really indicative of what it does. @cpojer up for an alias? Or just a rename, as we're getting close to a major release anyways |
I'd prefer an alias for now. |
Excuse the delay in reply. Thanks for taking my suggestion on board! |
Closing, since @jack-lewin's PR has been merged. Thanks again! |
just a note: the documentation is ahead of the latest release. Docs |
@makeshift3ds there should be a note: |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
What is the current behavior?
runTimersToTime implies that it is idempotent, since you are running to a time. But it actually advances by a time.
What is the expected behavior?
Either renamed to something more descriptive (
advanceTimersByTime
), or behaviour changed so that the following test fails.Please provide your exact Jest configuration and mention your Jest, node, yarn/npm version and operating system.
N/A
The text was updated successfully, but these errors were encountered: