History

Tobias Bosch 46b212706b refactor(core): change module semantics

This contains major changes to the compiler, bootstrap of the platforms
and test environment initialization.

Main part of #10043
Closes #10164

BREAKING CHANGE:
- Semantics and name of `@AppModule` (now `@NgModule`) changed quite a bit.
  This is actually not breaking as `@AppModules` were not part of rc.4.
  We will have detailed docs on `@NgModule` separately.
- `coreLoadAndBootstrap` and `coreBootstrap` can't be used any more (without migration support).
  Use `bootstrapModule` / `bootstrapModuleFactory` instead.
- All Components listed in routes have to be part of the `declarations` of an NgModule.
  Either directly on the bootstrap module / lazy loaded module, or in an NgModule imported by them.

2016-07-26 07:04:10 -07:00

animate/ts

repackaging: all the file moves

2016-05-01 20:51:00 -07:00

common/forms/ts/validators

chore(lint): Added license headers to most TypeScript files

2016-06-23 09:47:54 -07:00

compiler/ts/url_resolver

chore(lint): Added license headers to most TypeScript files

2016-06-23 09:47:54 -07:00

core

refactor(core): change module semantics

2016-07-26 07:04:10 -07:00

facade/ts/async

chore(lint): Added license headers to most TypeScript files

2016-06-23 09:47:54 -07:00

http/ts

repackaging: all the file moves

2016-05-01 20:51:00 -07:00

platform-browser/dom/debug/ts

fix: public api surface fixes + stability markers

2016-06-28 07:39:40 -07:00

router_deprecated/ts

fix(platform-browser): remove testing_e2e target (#10029 )

2016-07-13 10:10:02 -07:00

testing/ts

fix(testing): remove deprecated testing APIs (#9923 )

2016-07-11 16:04:32 -07:00

web_workers/ts

repackaging: all the file moves

2016-05-01 20:51:00 -07:00

README.md

repackaging: all the file moves

2016-05-01 20:51:00 -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.