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

fix(legacy-timers): Do not add setImmediate and clearImmediate if they do not exist in the global environment #11599

Merged
merged 1 commit into from Jun 22, 2021

Conversation

SimenB
Copy link
Member

@SimenB SimenB commented Jun 22, 2021

Summary

Fixes #11539

Test plan

🤷

… they do not exist in the global environment
@SimenB SimenB force-pushed the fake-timers-legacy-immediate branch from c79b3e0 to 91c932c Compare June 22, 2021 10:40
@codecov-commenter
Copy link

Codecov Report

Merging #11599 (91c932c) into master (6826764) will increase coverage by 0.00%.
The diff coverage is 100.00%.

Impacted file tree graph

@@           Coverage Diff           @@
##           master   #11599   +/-   ##
=======================================
  Coverage   69.00%   69.01%           
=======================================
  Files         312      312           
  Lines       16331    16335    +4     
  Branches     4730     4734    +4     
=======================================
+ Hits        11269    11273    +4     
  Misses       5034     5034           
  Partials       28       28           
Impacted Files Coverage Δ
packages/jest-fake-timers/src/legacyFakeTimers.ts 94.95% <100.00%> (+0.08%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6826764...91c932c. Read the comment docs.

@SimenB SimenB merged commit 6373529 into jestjs:master Jun 22, 2021
@SimenB SimenB deleted the fake-timers-legacy-immediate branch June 22, 2021 10:59
@github-actions
Copy link

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.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 23, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Legacy timers should check for presence in global before adding an immediate
3 participants