If you’re trying to observe when Angular runs the application synchronization, you might consider afterRender instead.
Yes, this’ll be due to the “fine grained reactivity”. ngDoCheck runs when the parent is refreshed. ChangeDetectorRef.markForCheck (and listeners) mark everything up to the root for check while signals will skip straight to the component with the signal read.
In v18, you also won’t need zone.run anymore to trigger change detection when you set a signal outside the zone. This works even for apps using ZoneJS
We’ll have a better picture of this as we gather feedback during experimental and dev preview phases. The path now is roughly: use OnPush, enable zone event coalescing, enable run coalescing, remove all NgZone.onMicrotaskEmpty/onStable uses. SSR is a bit more additional work.
Yes. We want to/will eventually have this in some form (ability to not automatically call markForCheck when a listener is triggered)
You’re exactly correct. This was done because we want the transition from OnPush to Zoneless to be as easy as possible. We want to/will eventually have an option that does not automatically mark for check when a listener is called.
This means that ZoneJS has some more behaviors than just running change detection. And zoneless needs a replacement for those "other features". The concept of "stability" needs a replacement in Zoneless as well (i.e. for SSR).
Sometimes errors might happen that you can resolve in a different window, such as an expired authentication cookie. Logging back in resolves the issue and in this case you could just refresh the page and it would load the page that was originally attempted instead of 404 again.
UrlTree redirects could not also include behavior options so the example had to create a new navigation instead. Redirects with options are now possible with github.com/angular/angular/c… and the documentation example was updated.
To be fair, any change to the exact timing of change detection can have this effect. Coalescing will be the default for new apps in v18.
On its own, the circular update isn’t a problem. If you had a condition around the update to only update it sometimes or it gets updated to a value that’s equal to the previous one. The problem is that the cycle is never broken.
👍 Okay, yea. It’s great to see the excitement and enthusiasm here. I just wanted to be sure expectations were appropriate so you aren’t disappointed with our ability to support you through the process.
To be clear about the Zoneless API: it is _not_ developer preview. Things being broken is entirely expected and we have no commitment to resolving any issues you encounter in a timely manner.
To be honest, I can't say for sure. The repo in its current state is using 17.1.0. When I update things to use 17.2.0-next.1, it does run change detection with the updated input. As far as I can tell, everything's WAI.
That version should have the required change. Do you have a reproduction? Kind of hard to tell what’s happening in the screenshot.
What version of Angular are you using? This required github.com/angular/angular/c… which has only been available since 17.1.2.
But also it looks like you're creating the component a second time in each test when you have it in beforeEach already. Is that intended?
Yes, but that’s actually kind of already the case. If you use OnPush in the components of your app, everything below them need to also follow OnPush semantics correctly or your app components will prevent the Default components in libraries from working.
The first example from the blog post felt satisfying and shows how far the framework has come in only the past few releases. stackblitz.com/edit/stackbli…
Standalone, self closing tags, input transform, tree shakable router features, input binding, view transitions, styles string.
