History

Tobias Bosch d2efac18ed feat(core): separate refs from vars.

Introduces `ref-` to give a name to an element or a directive (also works for `<template>` elements), and `let-` to introduce an input variable for a `<template>` element.

BREAKING CHANGE:
- `#...` 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.

Closes #7158

Closes #8264

2016-04-28 01:13:40 +00:00

animate/ts

docs(examples): add empty examples directory for api docs examples

2015-09-23 21:30:17 +00:00

common/forms/ts/validators

docs(*): Document a lot more symbols that are missing comments in our generated docs.

2015-12-15 03:04:48 +00:00

compiler/ts/url_resolver

feat(dart/transform): Use angular2/platform/browser as bootstrap lib

2016-03-21 00:58:17 +00:00

core

feat(core): separate refs from vars.

2016-04-28 01:13:40 +00:00

facade/ts/async

chore(test.typings): instrument against examples folder

2016-03-24 19:25:07 +00:00

http/ts

docs(examples): add empty examples directory for api docs examples

2015-09-23 21:30:17 +00:00

platform/dom/debug/ts

refactor(core): support non reflective bootstrap.

2016-04-20 11:34:11 -07:00

router/ts

feat(core): separate refs from vars.

2016-04-28 01:13:40 +00:00

testing/ts

revert(format): Revert "chore(format): update to latest formatter"

2016-04-12 09:41:01 -07:00

web_workers/ts

docs(examples): add empty examples directory for api docs examples

2015-09-23 21:30:17 +00:00

README.md

chore(examples): explain the purpose of these examples

2015-10-30 14:27:47 -07:00

README.md

API Examples

This folder contains small example apps that get in-lined into our API docs. These examples are written with idiomatic TypeScript, and are not transpiled to Dart. Each example contains tests for application behavior (as opposed to testing Angular's behavior) just like an Angular application developer would write.