From 10b21a4567fe657898d41cc89ac9ff06f0710742 Mon Sep 17 00:00:00 2001
From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com>
Date: Mon, 25 Nov 2024 07:17:10 +0000
Subject: [PATCH] Bump @angular/animations from 18.2.12 to 19.0.0 in
/web_embedding/ng-flutter (#2495)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Bumps [@angular/animations](https://github.com/angular/angular/tree/HEAD/packages/animations) from 18.2.12 to 19.0.0.
Sourced from Explore Angular v19 with a blog post from the Angular team: https://blog.angular.dev/meet-angular-v19-7b29dfd05b84 Angular directives, components and pipes are now standalone by default. TypeScript versions less than 5.5 are no longer supported. Timing changes for effects which are triggered outside of change detection run as part of
the change detection process instead of as a microtask. Depending on the
specifics of application/test setup, this can result in them executing
earlier or later (or requiring additional test steps to trigger; see below
examples). effects which are triggered during change detection (e.g. by input
signals) run earlier, before the component's template. The // To prevent projecting the default fallback content:
createComponent(MyComponent. { projectableNodes: [[document.createTextNode('')], [secondNode]] });Release notes
@âangular/animations
's releases.
v19.0.0
19.0.0 (2024-11-19)
Breaking Changes
compiler
this.foo
property reads no longer refer to template context variables. If you intended to read the template variable, do not use this.
.core
standalone: false
for declarations that are currently declared in @NgModule
s.ng update
for v19 will take care of this automatically.effect
API (in developer preview):
ExperimentalPendingTasks
has been renamed to PendingTasks
.autoDetect
feature of ComponentFixture
will now
attach the fixture to the ApplicationRef
. As a result, errors during
automatic change detection of the fixture be reported to the ErrorHandler
.
This change may cause custom error handlers to observe new failures that were previously unreported.createComponent
will now render default fallback with empty projectableNodes
.
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
.// The first ng-content will render the default fallback content if present
createComponent(MyComponent. { projectableNodes: [[], [secondNode]] });
Errors that are thrown during ApplicationRef.tick
will now be rethrown when using TestBed
. These errors should be
resolved by ensuring the test environment is set up correctly to
complete change detection successfully. There are two alternatives to
catch the errors:
... (truncated)
Sourced from @âangular/animations
's changelog.
19.0.0 (2024-11-19)
Blog post: https://blog.angular.dev/meet-angular-v19-7b29dfd05b84
Breaking Changes
compiler
this.foo
property reads no longer refer to template context variables. If you intended to read the template variable, do not usethis.
.core
Angular directives, components and pipes are now standalone by default.
- Specify
standalone: false
for declarations that are currently declared in@NgModule
s.ng update
for v19 will take care of this automatically.TypeScript versions less than 5.5 are no longer supported.
Timing changes for
effect
API (in developer preview):
effects which are triggered outside of change detection run as part of the change detection process instead of as a microtask. Depending on the specifics of application/test setup, this can result in them executing earlier or later (or requiring additional test steps to trigger; see below examples).
effects which are triggered during change detection (e.g. by input signals) run earlier, before the component's template.
ExperimentalPendingTasks
has been renamed toPendingTasks
.The
autoDetect
feature ofComponentFixture
will now attach the fixture to theApplicationRef
. As a result, errors during automatic change detection of the fixture be reported to theErrorHandler
. This change may cause custom error handlers to observe new failures that were previously unreported.
createComponent
will now render default fallback with emptyprojectableNodes
.
- When passing an empty array to
projectableNodes
in thecreateComponent
API, the default fallback content of theng-content
will be rendered if present. To prevent rendering the default content, passdocument.createTextNode('')
as aprojectableNode
.// 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]] });
Errors that are thrown during
ApplicationRef.tick
will now be rethrown when usingTestBed
. These errors should be resolved by ensuring the test environment is set up correctly to complete change detection successfully. There are two alternatives to catch the errors:
- Instead of waiting for automatic change detection to happen, trigger it synchronously and expect the error. For example, a jasmine test could write
expect(() => TestBed.inject(ApplicationRef).tick()).toThrow()
... (truncated)