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.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
- `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
- `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
- `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency
- `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions
Bumps the angular group in /webapp/wiremock with 12 updates:
18.2.2
18.2.3
18.2.2
18.2.3
18.2.2
18.2.3
18.2.2
18.2.3
18.2.2
18.2.3
18.2.2
18.2.3
18.2.2
18.2.3
18.2.2
18.2.3
18.2.2
18.2.3
18.2.2
18.2.3
18.2.2
18.2.3
18.2.2
18.2.3
Updates
@angular/animations
from 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/common
from 18.2.2 to 18.2.3Release notes
Sourced from
@angular/common
's releases.Changelog
Sourced from
@angular/common
's changelog.... (truncated)
Commits
de68e04
fix(http): Dynamicaly call the global fetch implementation (#57531)Updates
@angular/compiler
from 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/core
from 18.2.2 to 18.2.3Release notes
Sourced from
@angular/core
's releases.Changelog
Sourced from
@angular/core
's changelog.... (truncated)
Commits
93bdbbc
docs(docs-infra): Add dev-mode only mention forcore/global
(#57365)d9c1004
refactor(migrations): ensure control flow analysis of signal input migration ...bb29c8b
refactor(migrations): cleanup TODOs in signal input migration (#57566)3b7162d
docs: Add mention toENVIRONMENT_INITIALIZER
(#57464)3bc2867
docs(docs-infra): remove hash before link (#57351)Updates
@angular/forms
from 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-browser
from 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-dynamic
from 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/router
from 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-angular
from 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
f4db482
release: cut the v18.2.3 release4820766
fix(@angular-devkit/build-angular
): updatewebpack-dev-middleware
to7.4.2
Updates
@angular/cli
from 18.2.2 to 18.2.3Release notes
Sourced from
@angular/cli
's releases.Changelog
Sourced from
@angular/cli
's changelog.Commits
f4db482
release: cut the v18.2.3 release4820766
fix(@angular-devkit/build-angular
): updatewebpack-dev-middleware
to7.4.2
Updates
@angular/compiler-cli
from 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
582aac4
refactor(compiler-cli): Add support for inheritance in API extraction (#57588)4d8da40
Revert "refactor(compiler-cli): extract function overload separatly (#56489)"...c068045
docs(docs-infra): Add support for cross-links on API pages (#57346)9814767
refactor(compiler-cli): Add a map of every symbols used inside a package (#57...93bdbbc
docs(docs-infra): Add dev-mode only mention forcore/global
(#57365)8e1d6c7
refactor(compiler-cli): extract function overload separatly (#56489)Updates
@angular/localize
from 18.2.2 to 18.2.3Release notes
Sourced from
@angular/localize
's releases.Changelog
Sourced from
@angular/localize
's changelog.... (truncated)
Commits
f75429d
release: cut the v18.2.3 releasec91c377
release: bump Angular DevTools version to 1.0.18 (#57585)de68e04
fix(http): Dynamicaly call the global fetch implementation (#57531)2324d9b
docs: Fix 'EnvironmentInjector' description (#57582)b494e9b
build: update babel dependencies to v7.25.6 (#57634)5d7e446
build: update scorecard action dependencies (#57636)00c0876
docs(upgrade): change example wording on Input tutorial (#57625)9c3aeb9
docs(docs-infra): add support forextends
/implements
on API entries (#57588)582aac4
refactor(compiler-cli): Add support for inheritance in API extraction (#57588)5256016
docs(docs-infra): fix navigation between API pages (#57492)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show