History

Tobias Bosch 0a7d10ba55 refactor(core): separate reflective injector from Injector interface

BREAKING CHANGE:
- Injector was renamed into `ReflectiveInjector`,
  as `Injector` is only an abstract class with one method on it
- `Injector.getOptional()` was changed into `Injector.get(token, notFoundValue)`
  to make implementing injectors simpler
- `ViewContainerRef.createComponent` now takes an `Injector`
  instead of `ResolvedProviders`. If a reflective injector
  should be used, create one before calling this method.
  (e.g. via `ReflectiveInjector.resolveAndCreate(…)`.

2016-04-20 11:28:13 -07: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

refactor(core): separate reflective injector from Injector interface

2016-04-20 11:28:13 -07: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

feat(debug): replace DebugElement with new Debug DOM

2016-01-29 11:28:10 -08:00

router/ts

refactor(Location): out of router and into platform/common

2016-04-20 04:28:47 +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.