honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/modules/angular2/test/router/integration
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
..
impl refactor(core): separate reflective injector from Injector interface 2016-04-20 11:28:13 -07:00
README.md refactor(router): improve recognition and generation pipeline 2015-11-30 17:06:03 +00:00
async_route_spec.ts revert(format): Revert "chore(format): update to latest formatter" 2016-04-12 09:41:01 -07:00
auxiliary_route_spec.ts revert(format): Revert "chore(format): update to latest formatter" 2016-04-12 09:41:01 -07:00
bootstrap_spec.ts refactor(core): introduce ComponentFactory. 2016-04-20 11:27:26 -07:00
lifecycle_hook_spec.ts revert(format): Revert "chore(format): update to latest formatter" 2016-04-12 09:41:01 -07:00
navigation_spec.ts refactor(Location): out of router and into platform/common 2016-04-20 04:28:47 +00:00
redirect_route_spec.ts refactor(Location): out of router and into platform/common 2016-04-20 04:28:47 +00:00
router_link_spec.ts refactor(Location): out of router and into platform/common 2016-04-20 04:28:47 +00:00
sync_route_spec.ts revert(format): Revert "chore(format): update to latest formatter" 2016-04-12 09:41:01 -07:00
util.ts refactor(Location): out of router and into platform/common 2016-04-20 04:28:47 +00:00

README.md

Router integration tests

These tests only mock out Location, and otherwise use all the real parts of routing to ensure that various routing scenarios work as expected.

The Component Router in Angular 2 exposes only a handful of different options, but because they can be combined and nested in so many ways, it's difficult to rigorously test all the cases.

The address this problem, we introduce describeRouter, describeWith, and describeWithout.