feat(core): Move zoneless change detection to dev preview #60748
Conversation
This commit moves zoneless from experimental to developer preview. * Update tag on provider API * Remove "experimental" from provider name * Move documentation from "experimental features" to "Best practives -> Performance" (at least temporarily until there is a better place)
angular-robot
bot
added
detected: feature
|
Deployed adev-preview for d76fc5d to: https://ng-dev-previews-fw--pr-angular-angular-60748-adev-prev-5xnw4pq3.web.app Note: As new commits are pushed to this pull request, this link is updated after the preview is rebuilt. |
| @@ -11,19 +11,18 @@ The main advantages to removing ZoneJS as a dependency are: | |||
|
|
|||
| ## Enabling Zoneless in an application | |||
|
|
|||
| The API for enabling Zoneless is currently experimental. Neither the shape, nor the underlying behavior is stable and can change | |||
| in patch versions. There are known feature gaps, including the lack of an ergonomic API which prevents the application from serializing too early with Server Side Rendering. | |||
| The API for enabling Zoneless is currently in developer preview. Neither the shape of the API nor the underlying behavior are stable and can change in patch versions. | |||
There was a problem hiding this comment.
minor: grammar
| The API for enabling Zoneless is currently in developer preview. Neither the shape of the API nor the underlying behavior are stable and can change in patch versions. | |
| The API for enabling Zoneless is currently in developer preview. Neither the shape of the API nor the underlying behavior is stable and can change in patch versions. |
|
Great to see that zoneless is moving to developer preview! What I’m still missing, though, is communication around testing. A lot of existing tests rely on fakeAsync or waitForAsync, which don’t work without zone.js. This raises important questions: Is there a migration path? What’s the recommended approach to handle async behavior in tests going forward? If fakeAsync/waitForAsync are no longer supported, this could mean a substantial rewrite of many tests. I’d even argue that switching an application to zoneless is relatively straightforward — but updating the tests might be significantly more challenging. If there’s already an issue or discussion covering this topic, it would be great to link it here. Otherwise, happy to open one if that helps. |
|
You do not have to remove fakeAsync from your tests unless you want to purge the ZoneJs library entirely. It’s not much different from any other mock clock library. You could migrate to a different mock clock implementation like sinonJS or jasmine clock if you want. |
|
Thanks, I understand. Still, I wonder - if I choose to go zoneless in my app, wouldn’t it feel natural to do the same in my tests? It might be helpful to include a note in the docs explaining:
Would that be something worth adding? I’d be more than happy to help out with a PR if that’s helpful! |
|
Yes, absolutely. The testing documentation in general could use a good refresh and these would be good topics to cover. Some of them are already in the component testing scenarios page, though that page should be reviewed and updated as a whole. |
Very good. Then I have something to do :) |
This commit moves zoneless from experimental to developer preview.
Blocked by the following:
Follow up work: