Skip to content

refactor(core): Only log the UNEXPECTED_ZONEJS_PRESENT_IN_ZONELESS_MO… #62658

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

atscott
Copy link
Contributor

@atscott atscott commented Jul 15, 2025

…DE warning once

This reduces the number of times the UNEXPECTED_ZONEJS_PRESENT_IN_ZONELESS_MODE warning is logged. This warning is especially spammy in tests.

…DE warning once

This reduces the number of times the UNEXPECTED_ZONEJS_PRESENT_IN_ZONELESS_MODE warning
is logged. This warning is especially spammy in tests.
@atscott atscott added the target: patch This PR is targeted for the next patch release label Jul 15, 2025
@angular-robot angular-robot bot added the area: core Issues related to the framework runtime label Jul 15, 2025
@ngbot ngbot bot added this to the Backlog milestone Jul 15, 2025
@JeanMeche
Copy link
Member

JeanMeche commented Jul 15, 2025

Fwiw, this error being spammy is what lead me to investigate and land #62596.
I see some kind of value of it being spammy, it's a huge FIXME.

@atscott
Copy link
Contributor Author

atscott commented Jul 16, 2025

@JeanMeche that’s a fair point. I think one motivation for making it less spammy is that I would actually encourage and expect more Zoneless tests during migration (or even not).

With Zoneless becoming the default, it may be that only a few tests truly need to test something specific to the ZoneJs integration but the rest can/should potentially operate in Zoneless mode by default but not necessarily require two splitting those out into a different test target.

I also don’t think the original intent was to log on every test execution but for it to log once on app load.

I could see this both ways though…

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: core Issues related to the framework runtime target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants