349935a434
In an Angular CLI project scenario where projects only reference top-level source-files through the `tsconfig` `files` option, we currently do not migrate referenced source-files. This can be fixed checking all referenced source-files which aren't coming from an external library. This is similar to how `tslint` determines project source-files. PR Close #30269 |
||
|---|---|---|
| .. | ||
| 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>