Dynamicaly call the global fetch implementation (#57531)
19.0.0-next.2 (2024-08-28)
Breaking Changes
core
Render default fallback with empty projectableNodes.
When passing an empty array to projectableNodes in the createComponent API, the default fallback content of the ng-content will be rendered if present. To prevent rendering the default content, pass document.createTextNode('') as a projectableNode.
For example:
// The first ng-content will render the default fallback content if present
createComponent(MyComponent. { projectableNodes: [[], [secondNode]] });
// To prevent projecting the default fallback content:
createComponent(MyComponent. { projectableNodes: [[document.createTextNode('')], [secondNode]] });
The timers that are used for zone coalescing and hybrid
mode scheduling (which schedules an application state synchronization
when changes happen outside the Angular zone) will now run in the zone
above Angular rather than the root zone. This will mostly affect tests
which use fakeAsync: these timers will now be visible to fakeAsync
and can be affected by tick or flush.
elements
as part of switching away from custom CD behavior to the
hybrid scheduler, timing of change detection around custom elements has
changed subtly. These changes make elements more efficient, but can cause
tests which encoded assumptions about how or when elements would be checked
to require updating.
Dynamicaly call the global fetch implementation (#57531)
19.0.0-next.2 (2024-08-28)
Breaking Changes
core
Render default fallback with empty projectableNodes.
When passing an empty array to projectableNodes in the createComponent API, the default fallback content of the ng-content will be rendered if present. To prevent rendering the default content, pass document.createTextNode('') as a projectableNode.
For example:
// The first ng-content will render the default fallback content if present
createComponent(MyComponent. { projectableNodes: [[], [secondNode]] });
// To prevent projecting the default fallback content:
createComponent(MyComponent. { projectableNodes: [[document.createTextNode('')], [secondNode]] });
The timers that are used for zone coalescing and hybrid
mode scheduling (which schedules an application state synchronization
when changes happen outside the Angular zone) will now run in the zone
above Angular rather than the root zone. This will mostly affect tests
which use fakeAsync: these timers will now be visible to fakeAsync
and can be affected by tick or flush.
elements
as part of switching away from custom CD behavior to the
hybrid scheduler, timing of change detection around custom elements has
changed subtly. These changes make elements more efficient, but can cause
tests which encoded assumptions about how or when elements would be checked
to require updating.
Dynamicaly call the global fetch implementation (#57531)
19.0.0-next.2 (2024-08-28)
Breaking Changes
core
Render default fallback with empty projectableNodes.
When passing an empty array to projectableNodes in the createComponent API, the default fallback content of the ng-content will be rendered if present. To prevent rendering the default content, pass document.createTextNode('') as a projectableNode.
For example:
// The first ng-content will render the default fallback content if present
createComponent(MyComponent. { projectableNodes: [[], [secondNode]] });
// To prevent projecting the default fallback content:
createComponent(MyComponent. { projectableNodes: [[document.createTextNode('')], [secondNode]] });
The timers that are used for zone coalescing and hybrid
mode scheduling (which schedules an application state synchronization
when changes happen outside the Angular zone) will now run in the zone
above Angular rather than the root zone. This will mostly affect tests
which use fakeAsync: these timers will now be visible to fakeAsync
and can be affected by tick or flush.
elements
as part of switching away from custom CD behavior to the
hybrid scheduler, timing of change detection around custom elements has
changed subtly. These changes make elements more efficient, but can cause
tests which encoded assumptions about how or when elements would be checked
to require updating.
Dynamicaly call the global fetch implementation (#57531)
19.0.0-next.2 (2024-08-28)
Breaking Changes
core
Render default fallback with empty projectableNodes.
When passing an empty array to projectableNodes in the createComponent API, the default fallback content of the ng-content will be rendered if present. To prevent rendering the default content, pass document.createTextNode('') as a projectableNode.
For example:
// The first ng-content will render the default fallback content if present
createComponent(MyComponent. { projectableNodes: [[], [secondNode]] });
// To prevent projecting the default fallback content:
createComponent(MyComponent. { projectableNodes: [[document.createTextNode('')], [secondNode]] });
The timers that are used for zone coalescing and hybrid
mode scheduling (which schedules an application state synchronization
when changes happen outside the Angular zone) will now run in the zone
above Angular rather than the root zone. This will mostly affect tests
which use fakeAsync: these timers will now be visible to fakeAsync
and can be affected by tick or flush.
elements
as part of switching away from custom CD behavior to the
hybrid scheduler, timing of change detection around custom elements has
changed subtly. These changes make elements more efficient, but can cause
tests which encoded assumptions about how or when elements would be checked
to require updating.
Dynamicaly call the global fetch implementation (#57531)
19.0.0-next.2 (2024-08-28)
Breaking Changes
core
Render default fallback with empty projectableNodes.
When passing an empty array to projectableNodes in the createComponent API, the default fallback content of the ng-content will be rendered if present. To prevent rendering the default content, pass document.createTextNode('') as a projectableNode.
For example:
// The first ng-content will render the default fallback content if present
createComponent(MyComponent. { projectableNodes: [[], [secondNode]] });
// To prevent projecting the default fallback content:
createComponent(MyComponent. { projectableNodes: [[document.createTextNode('')], [secondNode]] });
The timers that are used for zone coalescing and hybrid
mode scheduling (which schedules an application state synchronization
when changes happen outside the Angular zone) will now run in the zone
above Angular rather than the root zone. This will mostly affect tests
which use fakeAsync: these timers will now be visible to fakeAsync
and can be affected by tick or flush.
elements
as part of switching away from custom CD behavior to the
hybrid scheduler, timing of change detection around custom elements has
changed subtly. These changes make elements more efficient, but can cause
tests which encoded assumptions about how or when elements would be checked
to require updating.
Dynamicaly call the global fetch implementation (#57531)
19.0.0-next.2 (2024-08-28)
Breaking Changes
core
Render default fallback with empty projectableNodes.
When passing an empty array to projectableNodes in the createComponent API, the default fallback content of the ng-content will be rendered if present. To prevent rendering the default content, pass document.createTextNode('') as a projectableNode.
For example:
// The first ng-content will render the default fallback content if present
createComponent(MyComponent. { projectableNodes: [[], [secondNode]] });
// To prevent projecting the default fallback content:
createComponent(MyComponent. { projectableNodes: [[document.createTextNode('')], [secondNode]] });
The timers that are used for zone coalescing and hybrid
mode scheduling (which schedules an application state synchronization
when changes happen outside the Angular zone) will now run in the zone
above Angular rather than the root zone. This will mostly affect tests
which use fakeAsync: these timers will now be visible to fakeAsync
and can be affected by tick or flush.
elements
as part of switching away from custom CD behavior to the
hybrid scheduler, timing of change detection around custom elements has
changed subtly. These changes make elements more efficient, but can cause
tests which encoded assumptions about how or when elements would be checked
to require updating.
Dynamicaly call the global fetch implementation (#57531)
19.0.0-next.2 (2024-08-28)
Breaking Changes
core
Render default fallback with empty projectableNodes.
When passing an empty array to projectableNodes in the createComponent API, the default fallback content of the ng-content will be rendered if present. To prevent rendering the default content, pass document.createTextNode('') as a projectableNode.
For example:
// The first ng-content will render the default fallback content if present
createComponent(MyComponent. { projectableNodes: [[], [secondNode]] });
// To prevent projecting the default fallback content:
createComponent(MyComponent. { projectableNodes: [[document.createTextNode('')], [secondNode]] });
The timers that are used for zone coalescing and hybrid
mode scheduling (which schedules an application state synchronization
when changes happen outside the Angular zone) will now run in the zone
above Angular rather than the root zone. This will mostly affect tests
which use fakeAsync: these timers will now be visible to fakeAsync
and can be affected by tick or flush.
elements
as part of switching away from custom CD behavior to the
hybrid scheduler, timing of change detection around custom elements has
changed subtly. These changes make elements more efficient, but can cause
tests which encoded assumptions about how or when elements would be checked
to require updating.
Dynamicaly call the global fetch implementation (#57531)
19.0.0-next.2 (2024-08-28)
Breaking Changes
core
Render default fallback with empty projectableNodes.
When passing an empty array to projectableNodes in the createComponent API, the default fallback content of the ng-content will be rendered if present. To prevent rendering the default content, pass document.createTextNode('') as a projectableNode.
For example:
// The first ng-content will render the default fallback content if present
createComponent(MyComponent. { projectableNodes: [[], [secondNode]] });
// To prevent projecting the default fallback content:
createComponent(MyComponent. { projectableNodes: [[document.createTextNode('')], [secondNode]] });
The timers that are used for zone coalescing and hybrid
mode scheduling (which schedules an application state synchronization
when changes happen outside the Angular zone) will now run in the zone
above Angular rather than the root zone. This will mostly affect tests
which use fakeAsync: these timers will now be visible to fakeAsync
and can be affected by tick or flush.
elements
as part of switching away from custom CD behavior to the
hybrid scheduler, timing of change detection around custom elements has
changed subtly. These changes make elements more efficient, but can cause
tests which encoded assumptions about how or when elements would be checked
to require updating.
Dynamicaly call the global fetch implementation (#57531)
19.0.0-next.2 (2024-08-28)
Breaking Changes
core
Render default fallback with empty projectableNodes.
When passing an empty array to projectableNodes in the createComponent API, the default fallback content of the ng-content will be rendered if present. To prevent rendering the default content, pass document.createTextNode('') as a projectableNode.
For example:
// The first ng-content will render the default fallback content if present
createComponent(MyComponent. { projectableNodes: [[], [secondNode]] });
// To prevent projecting the default fallback content:
createComponent(MyComponent. { projectableNodes: [[document.createTextNode('')], [secondNode]] });
The timers that are used for zone coalescing and hybrid
mode scheduling (which schedules an application state synchronization
when changes happen outside the Angular zone) will now run in the zone
above Angular rather than the root zone. This will mostly affect tests
which use fakeAsync: these timers will now be visible to fakeAsync
and can be affected by tick or flush.
elements
as part of switching away from custom CD behavior to the
hybrid scheduler, timing of change detection around custom elements has
changed subtly. These changes make elements more efficient, but can cause
tests which encoded assumptions about how or when elements would be checked
to require updating.
Dynamicaly call the global fetch implementation (#57531)
19.0.0-next.2 (2024-08-28)
Breaking Changes
core
Render default fallback with empty projectableNodes.
When passing an empty array to projectableNodes in the createComponent API, the default fallback content of the ng-content will be rendered if present. To prevent rendering the default content, pass document.createTextNode('') as a projectableNode.
For example:
// The first ng-content will render the default fallback content if present
createComponent(MyComponent. { projectableNodes: [[], [secondNode]] });
// To prevent projecting the default fallback content:
createComponent(MyComponent. { projectableNodes: [[document.createTextNode('')], [secondNode]] });
The timers that are used for zone coalescing and hybrid
mode scheduling (which schedules an application state synchronization
when changes happen outside the Angular zone) will now run in the zone
above Angular rather than the root zone. This will mostly affect tests
which use fakeAsync: these timers will now be visible to fakeAsync
and can be affected by tick or flush.
elements
as part of switching away from custom CD behavior to the
hybrid scheduler, timing of change detection around custom elements has
changed subtly. These changes make elements more efficient, but can cause
tests which encoded assumptions about how or when elements would be checked
to require updating.
Bumps the minor group in /frontend with 20 updates:
18.2.218.2.318.2.218.2.318.2.218.2.318.2.218.2.318.2.218.2.318.2.218.2.318.2.218.2.318.2.218.2.318.2.218.2.318.2.218.2.318.2.218.2.318.2.218.2.318.2.218.2.318.2.218.2.39.9.19.10.018.2.218.2.322.5.222.5.48.3.08.4.08.3.08.4.09.9.19.10.0Updates
@angular/animationsfrom 18.2.2 to 18.2.3Release notes
Sourced from
@angular/animations's releases.Changelog
Sourced from
@angular/animations's changelog.... (truncated)
Commits
Updates
@angular/cdkfrom 18.2.2 to 18.2.3Release notes
Sourced from
@angular/cdk's releases.Changelog
Sourced from
@angular/cdk's changelog.Commits
ed63b4erelease: cut the v18.2.3 release4a79052fix(material/tooltip): remove old IE workaround (#29674)5f57157build: bump up machine size (#29680)0f07b25fix(material/badge): resolve memory leak (#29676)5d93395fix(material/core): Fix incorrect color role mappings (#29655)fe3f30ffix(material/core): Allow system variables to be formatted for opacity (#29665)Updates
@angular/commonfrom 18.2.2 to 18.2.3Release notes
Sourced from
@angular/common's releases.Changelog
Sourced from
@angular/common's changelog.... (truncated)
Commits
de68e04fix(http): Dynamicaly call the global fetch implementation (#57531)Updates
@angular/compilerfrom 18.2.2 to 18.2.3Release notes
Sourced from
@angular/compiler's releases.Changelog
Sourced from
@angular/compiler's changelog.... (truncated)
Commits
Updates
@angular/corefrom 18.2.2 to 18.2.3Release notes
Sourced from
@angular/core's releases.Changelog
Sourced from
@angular/core's changelog.... (truncated)
Commits
93bdbbcdocs(docs-infra): Add dev-mode only mention forcore/global(#57365)d9c1004refactor(migrations): ensure control flow analysis of signal input migration ...bb29c8brefactor(migrations): cleanup TODOs in signal input migration (#57566)3b7162ddocs: Add mention toENVIRONMENT_INITIALIZER(#57464)3bc2867docs(docs-infra): remove hash before link (#57351)Updates
@angular/formsfrom 18.2.2 to 18.2.3Release notes
Sourced from
@angular/forms's releases.Changelog
Sourced from
@angular/forms's changelog.... (truncated)
Commits
Updates
@angular/platform-browserfrom 18.2.2 to 18.2.3Release notes
Sourced from
@angular/platform-browser's releases.Changelog
Sourced from
@angular/platform-browser's changelog.... (truncated)
Commits
Updates
@angular/platform-browser-dynamicfrom 18.2.2 to 18.2.3Release notes
Sourced from
@angular/platform-browser-dynamic's releases.Changelog
Sourced from
@angular/platform-browser-dynamic's changelog.... (truncated)
Commits
Updates
@angular/routerfrom 18.2.2 to 18.2.3Release notes
Sourced from
@angular/router's releases.Changelog
Sourced from
@angular/router's changelog.... (truncated)
Commits
Updates
@angular-devkit/build-angularfrom 18.2.2 to 18.2.3Release notes
Sourced from
@angular-devkit/build-angular's releases.Changelog
Sourced from
@angular-devkit/build-angular's changelog.Commits
f4db482release: cut the v18.2.3 release4820766fix(@angular-devkit/build-angular): updatewebpack-dev-middlewareto7.4.2Updates
@angular/clifrom 18.2.2 to 18.2.3Release notes
Sourced from
@angular/cli's releases.Changelog
Sourced from
@angular/cli's changelog.Commits
f4db482release: cut the v18.2.3 release4820766fix(@angular-devkit/build-angular): updatewebpack-dev-middlewareto7.4.2Updates
@angular/compiler-clifrom 18.2.2 to 18.2.3Release notes
Sourced from
@angular/compiler-cli's releases.Changelog
Sourced from
@angular/compiler-cli's changelog.... (truncated)
Commits
582aac4refactor(compiler-cli): Add support for inheritance in API extraction (#57588)4d8da40Revert "refactor(compiler-cli): extract function overload separatly (#56489)"...c068045docs(docs-infra): Add support for cross-links on API pages (#57346)9814767refactor(compiler-cli): Add a map of every symbols used inside a package (#57...93bdbbcdocs(docs-infra): Add dev-mode only mention forcore/global(#57365)8e1d6c7refactor(compiler-cli): extract function overload separatly (#56489)Updates
@angular/language-servicefrom 18.2.2 to 18.2.3Release notes
Sourced from
@angular/language-service's releases.Changelog
Sourced from
@angular/language-service's changelog.