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
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
Bumps the all-updates group with 21 updates:
17.3.0
17.3.1
17.3.0
17.3.1
17.3.0
17.3.1
17.3.0
17.3.1
17.3.0
17.3.1
17.3.0
17.3.1
17.3.0
17.3.1
5.7.3
5.7.4
5.7.3
5.7.4
7.8.0
7.8.2
10.1.0
10.1.1
7.2.2
7.3.1
17.3.0
17.3.2
17.3.0
17.3.2
17.3.0
17.3.1
17.3.0
17.3.1
5.7.3
5.7.4
7.3.1
7.4.0
7.3.1
7.4.0
48.2.1
48.2.2
5.4.2
5.4.3
Updates
@angular/cdk
from 17.3.0 to 17.3.1Release notes
Sourced from
@angular/cdk
's releases.Changelog
Sourced from
@angular/cdk
's changelog.Commits
1623d66
release: cut the v17.3.1 releaseef0a97e
build: bump node version on CI (#28752)31e3088
fix(cdk/drag-drop): optionally inject parent drag in preview and placeholder ...85b9424
docs(material/form-field): Update example to not call function in template (#...Updates
@angular/common
from 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/core
from 17.3.0 to 17.3.1Release notes
Sourced from
@angular/core
's releases.Changelog
Sourced from
@angular/core
's changelog.... (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...Updates
@angular/forms
from 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-browser
from 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-dynamic
from 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/router
from 17.3.0 to 17.3.1Release notes
Sourced from
@angular/router
's releases.Changelog
Sourced from
@angular/router
's changelog.... (truncated)
Commits
Updates
@capacitor/android
from 5.7.3 to 5.7.4Release notes
Sourced from
@capacitor/android
's releases.Changelog
Sourced from
@capacitor/android
's changelog.Commits
f8f2322
Release 5.7.430a32f4
fix(http): change proxy url generationUpdates
@capacitor/core
from 5.7.3 to 5.7.4Release notes
Sourced from
@capacitor/core
's releases.Changelog
Sourced from
@capacitor/core
's changelog.Commits
f8f2322
Release 5.7.430a32f4
fix(http): change proxy url generationUpdates
@ionic/angular
from 7.8.0 to 7.8.2Release notes
Sourced from
@ionic/angular
's releases.Changelog
Sourced from
@ionic/angular
's changelog.Commits
eeab96d
v7.8.2ca09238
chore(deps): update dependency@capacitor/core
to v5.7.4 (#29209)1be956b
chore(deps): update dependency@stencil/core
to v4.13.0 (#29203)8ad66c0
fix(searchbar): autocapitalize is initialized correctly (#29197)d1253c0
merge release-7.8.1 (#29188)7ca6b80
chore(): update package lock files4cd8fb1
v7.8.158d217d
fix(react): avoid definitely typed errors with@types/react
@18
(#29182)73d661a
chore(github-actions): use flexible options to update screenshots (#29044)fc5d692
chore(deps): update dependency@capacitor/core
to v5.7.3 (#29176)Updates
filesize
from 10.1.0 to 10.1.1Changelog
Sourced from filesize's changelog.
Commits
cf1dcb7
Version bump to release new types declaration4268a4e
Merge pull request #180 from abaltuta/rework-typesaf4a6ef
fix: types for partial now return a higher order functionfbfc87f
change: rework types to allow usages like Parameters<typeof filesize>334d549
Bump@babel/traverse
from 7.23.0 to 7.23.2 (#178)b5d1ea9
Updating README.mdfc5d968
Updating README.mdd80c457
Generating CHANGELOG.mdUpdates
ionicons
from 7.2.2 to 7.3.1Release notes
Sourced from ionicons's releases.
Changelog
Sourced from ionicons's changelog.
... (truncated)
Commits
8b041ec
v7.3.163e60ec
fix: filled ellipsis circle icons renders correctly (#1353)4350c67
chore(ionitron): add auto response for community feedback (#1352)b63d12b
docs: update readme to use latest and switch unpkg to jsdelivr (#1084)d09ddb6
docs(contributing): clarify icon contributions (#1351)1c3f59d
chore: use local version of lerna (#1349)fdd70c6
merge release-7.3.0d38cbac
merge release-7.3.030f23ae
chore(ci): pass env token7073258
chore(): update package lock filesUpdates
@angular-devkit/build-angular
from 17.3.0 to 17.3.2Release notes
Sourced from
@angular-devkit/build-angular
's releases.