Andrew Scott

[Andrew Scott @AScottAngular]

@naveedahmed @BrowserPerson https://t.co/3XBYcbHv2l it’s dev preview now

[Andrew Scott @AScottAngular]

@zoaibdev If you’re trying to observe when Angular runs the application synchronization, you might consider afterRender instead.

[Andrew Scott @AScottAngular]

@zoaibdev 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.

[Andrew Scott @AScottAngular]

@Arnoud_dv @Jean__Meche In v18, you also won’t need https://t.co/baKmV2GTo0 anymore to trigger change detection when you set a signal outside the zone. This works even for apps using ZoneJS

[Andrew Scott @AScottAngular]

@minijus @Jean__Meche 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.

[Andrew Scott @AScottAngular]

@Deku_Nattsu @Jean__Meche Yes. We want to/will eventually have this in some form (ability to not automatically call markForCheck when a listener is triggered)

[Andrew Scott @AScottAngular]

@jbnizet @Jean__Meche @Deku_Nattsu 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.

[Andrew Scott @AScottAngular]

@eugeniyoz @Jean__Meche 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).

[Andrew Scott @AScottAngular]

@mohanramphp @Enea_Jahollari 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.

[Andrew Scott @AScottAngular]

@viperoni8 @Enea_Jahollari 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 https://t.co/yT03p0DC3n and the documentation example was updated.

[Andrew Scott @AScottAngular]

@SergeyGultyayev @Jean__Meche @synalx @Enea_Jahollari 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.

[Andrew Scott @AScottAngular]

@eugeniyoz @pkozlowski_os @Jean__Meche 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.

[Andrew Scott @AScottAngular]

@SimonBitwise 👍 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.

[Andrew Scott @AScottAngular]

@SimonBitwise 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.

[Andrew Scott @AScottAngular]

@SimonBitwise https://t.co/Sc4g9cfP2t
https://t.co/lHAncqJIaC

[Andrew Scott @AScottAngular]

@SimonBitwise 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.

[Andrew Scott @AScottAngular]

@SimonBitwise That version should have the required change. Do you have a reproduction? Kind of hard to tell what’s happening in the screenshot.

[Andrew Scott @AScottAngular]

@JVAsays @JayCooperBell @brandontroberts @angular 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.

[Andrew Scott @AScottAngular]

@AlejandroRzJz @tomastrajan The first example from the blog post felt satisfying and shows how far the framework has come in only the past few releases. https://t.co/sXFdzlOzPw
Standalone, self closing tags, input transform, tree shakable router features, input binding, view transitions, styles string.

[Andrew Scott @AScottAngular]

@AlejandroRzJz @tomastrajan Thanks! We tried hard to strike a balance between power and simplicity and I think we found it!