Thanks to visit codestin.com
Credit goes to github.com

Skip to content

fix(core): Testing should not throw when Zone does not patch test FW … #61628

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

Closed
wants to merge 1 commit into from

Conversation

atscott
Copy link
Contributor

@atscott atscott commented May 22, 2025

…APIs

This prevents core/testing from throwing an error if ZoneJS is present but does not patch the test FW APIs such that fakeAsync works automatically. For example, there is currently no patching of the vitest APIs, so if you try to use Vitest with Zone on the page, it will throw.

…APIs

This prevents `core/testing` from throwing an error if ZoneJS is present
but does not patch the test FW APIs such that `fakeAsync` works
automatically. For example, there is currently no patching of the vitest
APIs, so if you try to use Vitest with Zone on the page, it will throw.
@atscott atscott added the target: rc This PR is targeted for the next release-candidate label May 22, 2025
@angular-robot angular-robot bot added the area: core Issues related to the framework runtime label May 22, 2025
@ngbot ngbot bot added this to the Backlog milestone May 22, 2025
@atscott atscott added the action: merge The PR is ready for merge by the caretaker label May 22, 2025
atscott added a commit that referenced this pull request May 22, 2025
…APIs (#61628)

This prevents `core/testing` from throwing an error if ZoneJS is present
but does not patch the test FW APIs such that `fakeAsync` works
automatically. For example, there is currently no patching of the vitest
APIs, so if you try to use Vitest with Zone on the page, it will throw.

PR Close #61628
@atscott
Copy link
Contributor Author

atscott commented May 22, 2025

This PR was merged into the repository by commit 3d4ddd2.

The changes were merged into the following branches: 20.0.x

@atscott atscott closed this May 22, 2025
thePunderWoman added a commit to thePunderWoman/angular that referenced this pull request May 23, 2025
@thePunderWoman thePunderWoman added action: cleanup The PR is in need of cleanup, either due to needing a rebase or in response to comments from reviews and removed action: merge The PR is ready for merge by the caretaker labels May 23, 2025
@thePunderWoman
Copy link
Contributor

@atscott This unfortunately broke CI for 20.0.x. I've reverted it, but you'll want to take a look.

thePunderWoman added a commit that referenced this pull request May 23, 2025
@atscott atscott closed this May 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
action: cleanup The PR is in need of cleanup, either due to needing a rebase or in response to comments from reviews area: core Issues related to the framework runtime target: rc This PR is targeted for the next release-candidate
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants