364250e7a6
Currently when someone runs `ng update` with the static-query migration, the migration can fail with an error saying that the `AOT` compiler could not be created. This can happen if the CLI project contains a test `tsconfig.json` that is picked up by the schematic. Due to the fact that spec tsconfig files cannot be ran with NGC (e.g. test components are not part of a module; not all source files are guaranteed to be included), test `tsconfig` projects will now use a new `test` migration strategy where all queries within tests are left untouched and a TODO is added. PR Close #30034 |
||
|---|---|---|
| .. | ||
| angular | ||
| google3 | ||
| BUILD.bazel | ||
| README.md | ||
| analyze_template.ts | ||
| index.ts | ||
README.md
Assignments to template variables
With Ivy, assignments to template variables are no longer supported as template variables are effectively constants.
This means that assignments to template variables will break your application once Ivy is enabled by default. For example:
<button *ngFor="let option of options"
(click)="option = 'newButtonText'">
{{ option }}
</button>
In the example from above, a value is assigned to the option
template variable on click. This will ultimately break your
application and therefore the logic needs to be adjusted to not
update the option variable, but rather the given element in
the options array:
<button *ngFor="let option of options; let idx = index"
(click)="options[idx] = 'newButtonText'">
{{ option }}
</button>