symbol feature detection for the compiler (#54711)
18.0.0-next.0 (2024-03-14)
Breaking Changes
core
OnPush views at the root of the application need to
be marked dirty for their host bindings to refresh. Previously, the host
bindings were refreshed for all root views without respecting the
OnPush change detection strategy.
The ComponentFixtureautoDetect feature will no
longer refresh the component's host view when the component is OnPush
and not marked dirty. This exposes existing issues in components which
claim to be OnPush but do not correctly call markForCheck when they
need to be refreshed. If this change causes test failures, the easiest
fix is to change the component to ChangeDetectionStrategy.Default.
When Angular runs change detection, it will continue to
refresh any views attached to ApplicationRef that are still marked for
check after one round completes. In rare cases, this can result in infinite
loops when certain patterns continue to mark views for check using
ChangeDetectorRef.detectChanges. This will be surfaced as a runtime
error with the NG0103 code.
The ComponentFixture.autoDetect feature now executes
change detection for the fixture within ApplicationRef.tick. This more
closely matches the behavior of how a component would refresh in
production. The order of component refresh in tests may be slightly
affected as a result, especially when dealing with additional components
attached to the application, such as dialogs. Tests sensitive to this
type of change (such as screenshot tests) may need to be updated.
Concretely, this change means that the component will refresh before
additional views attached to ApplicationRef (i.e. dialog components).
Prior to this change, the fixture component would refresh after other
views attached to the application.
The exact timing of change detection execution when
using event or run coalescing with NgZone is now the first of either
setTimeout or requestAnimationFrame. Code which relies on this
timing (usually by accident) will need to be adjusted. If a callback
needs to execute after change detection, we recommend afterNextRender
instead of something like setTimeout.
Newly created and views marked for check and reattached
symbol feature detection for the compiler (#54711)
18.0.0-next.0 (2024-03-14)
Breaking Changes
core
OnPush views at the root of the application need to
be marked dirty for their host bindings to refresh. Previously, the host
bindings were refreshed for all root views without respecting the
OnPush change detection strategy.
The ComponentFixtureautoDetect feature will no
longer refresh the component's host view when the component is OnPush
and not marked dirty. This exposes existing issues in components which
claim to be OnPush but do not correctly call markForCheck when they
need to be refreshed. If this change causes test failures, the easiest
fix is to change the component to ChangeDetectionStrategy.Default.
When Angular runs change detection, it will continue to
refresh any views attached to ApplicationRef that are still marked for
check after one round completes. In rare cases, this can result in infinite
loops when certain patterns continue to mark views for check using
ChangeDetectorRef.detectChanges. This will be surfaced as a runtime
error with the NG0103 code.
The ComponentFixture.autoDetect feature now executes
change detection for the fixture within ApplicationRef.tick. This more
closely matches the behavior of how a component would refresh in
production. The order of component refresh in tests may be slightly
affected as a result, especially when dealing with additional components
attached to the application, such as dialogs. Tests sensitive to this
type of change (such as screenshot tests) may need to be updated.
Concretely, this change means that the component will refresh before
additional views attached to ApplicationRef (i.e. dialog components).
Prior to this change, the fixture component would refresh after other
views attached to the application.
The exact timing of change detection execution when
using event or run coalescing with NgZone is now the first of either
setTimeout or requestAnimationFrame. Code which relies on this
timing (usually by accident) will need to be adjusted. If a callback
needs to execute after change detection, we recommend afterNextRender
instead of something like setTimeout.
Newly created and views marked for check and reattached
symbol feature detection for the compiler (#54711)
18.0.0-next.0 (2024-03-14)
Breaking Changes
core
OnPush views at the root of the application need to
be marked dirty for their host bindings to refresh. Previously, the host
bindings were refreshed for all root views without respecting the
OnPush change detection strategy.
The ComponentFixtureautoDetect feature will no
longer refresh the component's host view when the component is OnPush
and not marked dirty. This exposes existing issues in components which
claim to be OnPush but do not correctly call markForCheck when they
need to be refreshed. If this change causes test failures, the easiest
fix is to change the component to ChangeDetectionStrategy.Default.
When Angular runs change detection, it will continue to
refresh any views attached to ApplicationRef that are still marked for
check after one round completes. In rare cases, this can result in infinite
loops when certain patterns continue to mark views for check using
ChangeDetectorRef.detectChanges. This will be surfaced as a runtime
error with the NG0103 code.
The ComponentFixture.autoDetect feature now executes
change detection for the fixture within ApplicationRef.tick. This more
closely matches the behavior of how a component would refresh in
production. The order of component refresh in tests may be slightly
affected as a result, especially when dealing with additional components
attached to the application, such as dialogs. Tests sensitive to this
type of change (such as screenshot tests) may need to be updated.
Concretely, this change means that the component will refresh before
additional views attached to ApplicationRef (i.e. dialog components).
Prior to this change, the fixture component would refresh after other
views attached to the application.
The exact timing of change detection execution when
using event or run coalescing with NgZone is now the first of either
setTimeout or requestAnimationFrame. Code which relies on this
timing (usually by accident) will need to be adjusted. If a callback
needs to execute after change detection, we recommend afterNextRender
instead of something like setTimeout.
Newly created and views marked for check and reattached
... (truncated)
Commits
c078820 fix(compiler): capture data bindings for content projection purposes in block...
symbol feature detection for the compiler (#54711)
18.0.0-next.0 (2024-03-14)
Breaking Changes
core
OnPush views at the root of the application need to
be marked dirty for their host bindings to refresh. Previously, the host
bindings were refreshed for all root views without respecting the
OnPush change detection strategy.
The ComponentFixtureautoDetect feature will no
longer refresh the component's host view when the component is OnPush
and not marked dirty. This exposes existing issues in components which
claim to be OnPush but do not correctly call markForCheck when they
need to be refreshed. If this change causes test failures, the easiest
fix is to change the component to ChangeDetectionStrategy.Default.
When Angular runs change detection, it will continue to
refresh any views attached to ApplicationRef that are still marked for
check after one round completes. In rare cases, this can result in infinite
loops when certain patterns continue to mark views for check using
ChangeDetectorRef.detectChanges. This will be surfaced as a runtime
error with the NG0103 code.
The ComponentFixture.autoDetect feature now executes
change detection for the fixture within ApplicationRef.tick. This more
closely matches the behavior of how a component would refresh in
production. The order of component refresh in tests may be slightly
affected as a result, especially when dealing with additional components
attached to the application, such as dialogs. Tests sensitive to this
type of change (such as screenshot tests) may need to be updated.
Concretely, this change means that the component will refresh before
additional views attached to ApplicationRef (i.e. dialog components).
Prior to this change, the fixture component would refresh after other
views attached to the application.
The exact timing of change detection execution when
using event or run coalescing with NgZone is now the first of either
setTimeout or requestAnimationFrame. Code which relies on this
timing (usually by accident) will need to be adjusted. If a callback
needs to execute after change detection, we recommend afterNextRender
instead of something like setTimeout.
Newly created and views marked for check and reattached
... (truncated)
Commits
e70228a refactor(core): Add hydration missmatch on the component rather than the node...
1f5ab96 refactor(core): allow passing an environment injector while creating a view (...
c078820 fix(compiler): capture data bindings for content projection purposes in block...
symbol feature detection for the compiler (#54711)
18.0.0-next.0 (2024-03-14)
Breaking Changes
core
OnPush views at the root of the application need to
be marked dirty for their host bindings to refresh. Previously, the host
bindings were refreshed for all root views without respecting the
OnPush change detection strategy.
The ComponentFixtureautoDetect feature will no
longer refresh the component's host view when the component is OnPush
and not marked dirty. This exposes existing issues in components which
claim to be OnPush but do not correctly call markForCheck when they
need to be refreshed. If this change causes test failures, the easiest
fix is to change the component to ChangeDetectionStrategy.Default.
When Angular runs change detection, it will continue to
refresh any views attached to ApplicationRef that are still marked for
check after one round completes. In rare cases, this can result in infinite
loops when certain patterns continue to mark views for check using
ChangeDetectorRef.detectChanges. This will be surfaced as a runtime
error with the NG0103 code.
The ComponentFixture.autoDetect feature now executes
change detection for the fixture within ApplicationRef.tick. This more
closely matches the behavior of how a component would refresh in
production. The order of component refresh in tests may be slightly
affected as a result, especially when dealing with additional components
attached to the application, such as dialogs. Tests sensitive to this
type of change (such as screenshot tests) may need to be updated.
Concretely, this change means that the component will refresh before
additional views attached to ApplicationRef (i.e. dialog components).
Prior to this change, the fixture component would refresh after other
views attached to the application.
The exact timing of change detection execution when
using event or run coalescing with NgZone is now the first of either
setTimeout or requestAnimationFrame. Code which relies on this
timing (usually by accident) will need to be adjusted. If a callback
needs to execute after change detection, we recommend afterNextRender
instead of something like setTimeout.
Newly created and views marked for check and reattached
symbol feature detection for the compiler (#54711)
18.0.0-next.0 (2024-03-14)
Breaking Changes
core
OnPush views at the root of the application need to
be marked dirty for their host bindings to refresh. Previously, the host
bindings were refreshed for all root views without respecting the
OnPush change detection strategy.
The ComponentFixtureautoDetect feature will no
longer refresh the component's host view when the component is OnPush
and not marked dirty. This exposes existing issues in components which
claim to be OnPush but do not correctly call markForCheck when they
need to be refreshed. If this change causes test failures, the easiest
fix is to change the component to ChangeDetectionStrategy.Default.
When Angular runs change detection, it will continue to
refresh any views attached to ApplicationRef that are still marked for
check after one round completes. In rare cases, this can result in infinite
loops when certain patterns continue to mark views for check using
ChangeDetectorRef.detectChanges. This will be surfaced as a runtime
error with the NG0103 code.
The ComponentFixture.autoDetect feature now executes
change detection for the fixture within ApplicationRef.tick. This more
closely matches the behavior of how a component would refresh in
production. The order of component refresh in tests may be slightly
affected as a result, especially when dealing with additional components
attached to the application, such as dialogs. Tests sensitive to this
type of change (such as screenshot tests) may need to be updated.
Concretely, this change means that the component will refresh before
additional views attached to ApplicationRef (i.e. dialog components).
Prior to this change, the fixture component would refresh after other
views attached to the application.
The exact timing of change detection execution when
using event or run coalescing with NgZone is now the first of either
setTimeout or requestAnimationFrame. Code which relies on this
timing (usually by accident) will need to be adjusted. If a callback
needs to execute after change detection, we recommend afterNextRender
instead of something like setTimeout.
Newly created and views marked for check and reattached
symbol feature detection for the compiler (#54711)
18.0.0-next.0 (2024-03-14)
Breaking Changes
core
OnPush views at the root of the application need to
be marked dirty for their host bindings to refresh. Previously, the host
bindings were refreshed for all root views without respecting the
OnPush change detection strategy.
The ComponentFixtureautoDetect feature will no
longer refresh the component's host view when the component is OnPush
and not marked dirty. This exposes existing issues in components which
claim to be OnPush but do not correctly call markForCheck when they
need to be refreshed. If this change causes test failures, the easiest
fix is to change the component to ChangeDetectionStrategy.Default.
When Angular runs change detection, it will continue to
refresh any views attached to ApplicationRef that are still marked for
check after one round completes. In rare cases, this can result in infinite
loops when certain patterns continue to mark views for check using
ChangeDetectorRef.detectChanges. This will be surfaced as a runtime
error with the NG0103 code.
The ComponentFixture.autoDetect feature now executes
change detection for the fixture within ApplicationRef.tick. This more
closely matches the behavior of how a component would refresh in
production. The order of component refresh in tests may be slightly
affected as a result, especially when dealing with additional components
attached to the application, such as dialogs. Tests sensitive to this
type of change (such as screenshot tests) may need to be updated.
Concretely, this change means that the component will refresh before
additional views attached to ApplicationRef (i.e. dialog components).
Prior to this change, the fixture component would refresh after other
views attached to the application.
The exact timing of change detection execution when
using event or run coalescing with NgZone is now the first of either
setTimeout or requestAnimationFrame. Code which relies on this
timing (usually by accident) will need to be adjusted. If a callback
needs to execute after change detection, we recommend afterNextRender
instead of something like setTimeout.
Newly created and views marked for check and reattached
symbol feature detection for the compiler (#54711)
18.0.0-next.0 (2024-03-14)
Breaking Changes
core
OnPush views at the root of the application need to
be marked dirty for their host bindings to refresh. Previously, the host
bindings were refreshed for all root views without respecting the
OnPush change detection strategy.
The ComponentFixtureautoDetect feature will no
longer refresh the component's host view when the component is OnPush
and not marked dirty. This exposes existing issues in components which
claim to be OnPush but do not correctly call markForCheck when they
need to be refreshed. If this change causes test failures, the easiest
fix is to change the component to ChangeDetectionStrategy.Default.
When Angular runs change detection, it will continue to
refresh any views attached to ApplicationRef that are still marked for
check after one round completes. In rare cases, this can result in infinite
loops when certain patterns continue to mark views for check using
ChangeDetectorRef.detectChanges. This will be surfaced as a runtime
error with the NG0103 code.
The ComponentFixture.autoDetect feature now executes
change detection for the fixture within ApplicationRef.tick. This more
closely matches the behavior of how a component would refresh in
production. The order of component refresh in tests may be slightly
affected as a result, especially when dealing with additional components
attached to the application, such as dialogs. Tests sensitive to this
type of change (such as screenshot tests) may need to be updated.
Concretely, this change means that the component will refresh before
additional views attached to ApplicationRef (i.e. dialog components).
Prior to this change, the fixture component would refresh after other
views attached to the application.
The exact timing of change detection execution when
using event or run coalescing with NgZone is now the first of either
setTimeout or requestAnimationFrame. Code which relies on this
timing (usually by accident) will need to be adjusted. If a callback
needs to execute after change detection, we recommend afterNextRender
instead of something like setTimeout.
Newly created and views marked for check and reattached
symbol feature detection for the compiler (#54711)
18.0.0-next.0 (2024-03-14)
Breaking Changes
core
OnPush views at the root of the application need to
be marked dirty for their host bindings to refresh. Previously, the host
bindings were refreshed for all root views without respecting the
OnPush change detection strategy.
The ComponentFixtureautoDetect feature will no
longer refresh the component's host view when the component is OnPush
and not marked dirty. This exposes existing issues in components which
claim to be OnPush but do not correctly call markForCheck when they
need to be refreshed. If this change ...
_Description has been truncated_
dependabot[bot]
commented
7 months ago
Bumps the angular group with 11 updates:
17.3.017.3.117.3.017.3.117.3.017.3.117.3.017.3.117.3.017.3.117.3.017.3.117.3.017.3.117.3.017.3.117.3.017.3.217.3.017.3.217.3.017.3.1Updates
@angular/animationsfrom 17.3.0 to 17.3.1Release notes
Sourced from
@angular/animations's releases.Changelog
Sourced from
@angular/animations's changelog.... (truncated)
Commits
Updates
@angular/commonfrom 17.3.0 to 17.3.1Release notes
Sourced from
@angular/common's releases.Changelog
Sourced from
@angular/common's changelog.... (truncated)
Commits
Updates
@angular/compilerfrom 17.3.0 to 17.3.1Release notes
Sourced from
@angular/compiler's releases.Changelog
Sourced from
@angular/compiler's changelog.... (truncated)
Commits
c078820fix(compiler): capture data bindings for content projection purposes in block...Updates
@angular/corefrom 17.3.0 to 17.3.1Release notes
Sourced from
@angular/core's releases.Changelog
Sourced from
@angular/core's changelog.... (truncated)
Commits
e70228arefactor(core): Add hydration missmatch on the component rather than the node...1f5ab96refactor(core): allow passing an environment injector while creating a view (...c078820fix(compiler): capture data bindings for content projection purposes in block...Updates
@angular/formsfrom 17.3.0 to 17.3.1Release notes
Sourced from
@angular/forms's releases.Changelog
Sourced from
@angular/forms's changelog.... (truncated)
Commits
Updates
@angular/platform-browserfrom 17.3.0 to 17.3.1Release notes
Sourced from
@angular/platform-browser's releases.Changelog
Sourced from
@angular/platform-browser's changelog.... (truncated)
Commits
Updates
@angular/platform-browser-dynamicfrom 17.3.0 to 17.3.1Release notes
Sourced from
@angular/platform-browser-dynamic's releases.Changelog
Sourced from
@angular/platform-browser-dynamic's changelog.... (truncated)
Commits
Updates
@angular/routerfrom 17.3.0 to 17.3.1Release notes
Sourced from
@angular/router's releases.Changelog
Sourced from
@angular/router's changelog.... (truncated)
Commits
Updates
@angular-devkit/build-angularfrom 17.3.0 to 17.3.2Release notes
Sourced from
@angular-devkit/build-angular's releases.Changelog
Sourced from
@angular-devkit/build-angular's changelog.... (truncated)
Commits
8a6550drelease: cut the v17.3.2 release59fba38fix(@angular-devkit/build-angular): ensure proper resolution of linked SCSS f...27dd8f2fix(@angular-devkit/build-angular): service-worker references non-existent na...935f931fix(@schematics/angular): rename SSR port env variablec12907dfix(@angular-devkit/build-angular): updatewebpack-dev-middlewareto6.1.2c9d4360fix(@angular-devkit/build-angular):Internal server error: Invalid URLwhen...1a3257arefactor(@schematics/angular): Use MaybeAsync and GuardResult types to reduce...7041511release: cut the v17.3.1 release198ca9afix(@schematics/angular): improve Sass format clarity for application style o...2809971fix(@angular-devkit/build-angular): only generateserverdirectory when SSR...Updates
@angular/clifrom 17.3.0 to 17.3.2Release notes
Sourced from
@angular/cli's releases.Changelog
Sourced from
@angular/cli's changelog.... (truncated)
Commits
8a6550drelease: cut the v17.3.2 release59fba38fix(@angular-devkit/build-angular): ensure proper resolution of linked SCSS f...27dd8f2fix(@angular-devkit/build-angular): service-worker references non-existent na...935f931fix(@schematics/angular): rename SSR port env variablec12907dfix(@angular-devkit/build-angular): updatewebpack-dev-middlewareto6.1.2c9d4360fix(@angular-devkit/build-angular):Internal server error: Invalid URLwhen...1a3257arefactor(@schematics/angular): Use MaybeAsync and GuardResult types to reduce...7041511release: cut the v17.3.1 release198ca9afix(@schematics/angular): improve Sass format clarity for application style o...2809971fix(@angular-devkit/build-angular): only generateserverdirectory when SSR...Updates
@angular/compiler-clifrom 17.3.0 to 17.3.1Release notes
Sourced from
@angular/compiler-cli's releases.Changelog
Sourced from
@angular/compiler-cli's changelog.