refactor(core): Update zone and zoneless error to be a warning instead #63457
+7
−5
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.
This updates the error thrown when both
provideZoneChangeDetection
andprovideZonelessChangeDetection
are both used in the application providers to be a warning instead. The reasons for this are twofold:provideZoneChangeDetection
when the zoneless provider exists. This change will prevent that from causing an errorinitTestEnvironment
may have a default but individual tests might want to use a different one. The same logic might apply to applications in some environments.