chore(CHANGELOG): Fix breaking changes description
Adds more info and examples about how ngFor is affected by the change.
This commit is contained in:
parent
70b23ae2ca
commit
073ec0a7eb
20
CHANGELOG.md
20
CHANGELOG.md
|
@ -18,12 +18,22 @@
|
||||||
|
|
||||||
### BREAKING CHANGES
|
### BREAKING CHANGES
|
||||||
|
|
||||||
* - `#...` now always means `ref-`.
|
The reference `#...` now always means `ref-`.
|
||||||
- `<template #abc>` now defines a reference to the TemplateRef, instead of an input variable used inside of the template.
|
|
||||||
- `#...` inside of a *ngIf, … directives is deprecated.
|
|
||||||
Use `let …` instead.
|
|
||||||
- `var-...` is deprecated. Replace with `let-...` for `<template>` elements and `ref-` for non `<template>` elements.
|
|
||||||
|
|
||||||
|
**Before:**
|
||||||
|
- Outside of `ngFor`, a `#...` meant a reference.
|
||||||
|
- Inside of `ngFor`, it meant a local variable.
|
||||||
|
|
||||||
|
This was pattern was confusing.
|
||||||
|
|
||||||
|
**After:**
|
||||||
|
|
||||||
|
- `<template #abc>` now defines a reference to a TemplateRef, instead of an input variable used inside of the template.
|
||||||
|
- Inside of structural directives that declare local variables, such as `*ngFor`, usage of `#...` is deprecated. Use `let` instead.
|
||||||
|
- `<div *ngFor="#item of items">` now becomes `<div *ngFor="let item of items">`
|
||||||
|
- `var-...` is deprecated.
|
||||||
|
- use `#` or a `ref-` outside of `*ngFor`
|
||||||
|
- for `ngFor`, use the syntax: `<template ngFor let-... [ngForOf]="...">`
|
||||||
|
|
||||||
|
|
||||||
<a name="2.0.0-beta.16"></a>
|
<a name="2.0.0-beta.16"></a>
|
||||||
|
|
Loading…
Reference in New Issue