Commits on Apr 16, 2024

1. fix(core): Angular should not ignore changes that happen outside the … …

   …zone
   
   When Angular receives a clear indication that change detection should
   run again, this should not be ignored, regardless of what Zone it
   happened in. This change updates the default change detection scheduling
   approach of Zone-based applications to ensure a change detection will
   run when these events happen outside the Angular zone (which includes,
   for example, updating a signal that's read in a template, setting an
   input of a `ComponentRef`, attaching a view marked for check, calling
   `ChangeDetectorRef.markForCheck`, etc.).
   
   This does not apply to applications using `NoopNgZone` or those which
   have a custom `NgZone` implementation without ZoneJS.
   
   The impact of this change will most often be seen in existing unit tests. Tests
   execute outside the Angular Zone and this can mean that state in the
   test is not fully recognized by Angular. Now that Angular will ensure
   change detection _does_ run, even when the state update originates from
   outside the zone, tests may observe additional rounds of change
   detection compared to the previous behavior. Often, this should be seen
   as more correct and the test should be updated, but in cases where it is
   too much effort to debug, the test can revert to the old behavior by adding
   `provideZoneChangeDetection({schedulingMode: NgZoneSchedulingMode.NgZoneOnly})`
   to the `TestBed` providers.
   
   fixes angular#55238
   fixes angular#53844
   fixes angular#53841
   fixes angular#52610
   fixes angular#53566
   fixes angular#52940
   fixes angular#51970
   fixes angular#51768
   fixes angular#50702
   fixes angular#50259
   fixes angular#50266
   fixes angular#50160
   fixes angular#49940
   fixes angular#49398
   fixes angular#48890
   fixes angular#48608
   fixes angular#45105
   fixes angular#42241
   fixes angular#41553
   fixes angular#37223
   fixes angular#37062
   fixes angular#35579
   fixes angular#31695
   fixes angular#24728
   fixes angular#23697
   fixes angular#19814
   fixes angular#13957
   fixes angular#11565
   fixes angular#15770
   fixes angular#15946
   fixes angular#18254
   fixes angular#19731
   fixes angular#20112
   fixes angular#22472
   fixes angular#23697
   fixes angular#24727
   fixes angular#47236
   
   BREAKING CHANGE:
   
   Angular will ensure change detection runs, even when the state update originates from
   outside the zone, tests may observe additional rounds of change
   detection compared to the previous behavior.
   
   This change will be more likely to impact existing unit tests.
   This should usually be seen as more correct and the test should be updated,
   but in cases where it is too much effort to debug, the test can revert to the old behavior by adding
   `provideZoneChangeDetection({schedulingMode: NgZoneSchedulingMode.NgZoneOnly})`
   to the `TestBed` providers.
   
   Similarly, applications which may want to update state outside the zone
   and _not_ trigger change detection can add
   `provideZoneChangeDetection({schedulingMode: NgZoneSchedulingMode.NgZoneOnly})`
   to the providers in `bootstrapApplication` or add
   `schedulingMode: NgZoneSchedulingMode.NgZoneOnly` to the
   `BootstrapOptions` of `bootstrapModule`.

   

   atscott committed Apr 16, 2024
   Configuration menu

   • View commit details
   • Copy full SHA for 3f48dab
   • Browse repository at this point

   Copy the full SHA

   3f48dab View commit details

   Browse the repository at this point in the history