angular/packages/core/test/bundling
Andrew Scott 606de5166e refactor(core): newly created and any dirty views should get refreshed during CD (#53022)
When a view has the `Dirty` flag and is reattached, we should ensure that it is
reached and refreshed during the next change detection run from above.

In addition, when a view is created and attached, we should ensure that it is reached
and refreshed during change detection. This can happen if the view is
created and attached outside a change run or when it is created and
attached after its insertion view was already checked. In both cases, we
should ensure that the view is reached and refreshed during either the
current change detection or the next one (if change detection is not
already running).

We can achieve this by creating all views with the `Dirty` flag set.

However, this does happen to be a breaking change in some scenarios.
The one identified internally was actually depending on change detection
_not_ running immediately because it relied on an input value that was
set using `ngModel`. Because `ngModel` sets its value in a `Promise`, it
is not available until the _next_ change detection cycle. Ensuring
created views run in the current change change detection will result in
different behavior in this case.

Making option the default is the solution to #52928. That will have to
wait for a major version.

PR Close #53022
2023-12-14 09:17:49 -08:00
..
animation_world refactor(core): Remove detectChanges private export (#52875) 2023-11-14 21:05:42 +00:00
animations fix(core): Multiple subscribers to ApplicationRef.isStable should all see values (#53541) 2023-12-13 11:26:51 -08:00
animations-standalone fix(core): Multiple subscribers to ApplicationRef.isStable should all see values (#53541) 2023-12-13 11:26:51 -08:00
core_all build: update dev-infra packages and account for build-tooling split from ng-dev (#46976) 2022-08-02 09:37:37 -07:00
cyclic_import fix(core): Multiple subscribers to ApplicationRef.isStable should all see values (#53541) 2023-12-13 11:26:51 -08:00
defer refactor(core): newly created and any dirty views should get refreshed during CD (#53022) 2023-12-14 09:17:49 -08:00
forms_reactive refactor(core): newly created and any dirty views should get refreshed during CD (#53022) 2023-12-14 09:17:49 -08:00
forms_template_driven refactor(core): newly created and any dirty views should get refreshed during CD (#53022) 2023-12-14 09:17:49 -08:00
hello_world fix(core): Multiple subscribers to ApplicationRef.isStable should all see values (#53541) 2023-12-13 11:26:51 -08:00
hello_world_i18n test(core): convert remaining bundling tests to not use renderComponent (#46559) 2022-06-28 21:37:45 -07:00
hydration fix(core): Multiple subscribers to ApplicationRef.isStable should all see values (#53541) 2023-12-13 11:26:51 -08:00
image-directive feat(core): add warnings for oversized images and lazy-lcp (#51846) 2023-10-06 12:14:32 -07:00
injection build: lock file maintenance (#50227) 2023-05-10 11:32:43 -07:00
router refactor(core): newly created and any dirty views should get refreshed during CD (#53022) 2023-12-14 09:17:49 -08:00
standalone_bootstrap fix(core): Multiple subscribers to ApplicationRef.isStable should all see values (#53541) 2023-12-13 11:26:51 -08:00
todo refactor(core): newly created and any dirty views should get refreshed during CD (#53022) 2023-12-14 09:17:49 -08:00
todo_i18n refactor(core): Remove detectChanges private export (#52875) 2023-11-14 21:05:42 +00:00
README.md fix(core): remove individual commands for updating gold files (#45198) 2022-03-01 19:16:53 +00:00

Bundle

js_expected_symbol_test

This folder contains tests which assert that most of the code is tree shaken away. This is asserted by keeping gold files of all symbols which are expected to be retained. When doing renaming it is often necessary to update the gold files; to do so use these scripts:

yarn run symbol-extractor:check
yarn run symbol-extractor:update