Skip to content

Commit

Permalink
chore(CHANGELOG): Fix breaking changes description
Browse files Browse the repository at this point in the history
Adds more info and examples about how ngFor is affected by the change.
  • Loading branch information
naomiblack committed Apr 29, 2016
1 parent 70b23ae commit 073ec0a
Showing 1 changed file with 15 additions and 5 deletions.
20 changes: 15 additions & 5 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,12 +18,22 @@

### BREAKING CHANGES

* - `#...` 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.
The reference `#...` now always means `ref-`.

**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>
Expand Down

0 comments on commit 073ec0a

Please sign in to comment.