6fc267f22c
Previously these symbols were exposed via platform-browser-dynamic, then we merged then into platform-browser thinking that tools would know how to shake off the compiler and other dynamic bits not used with the offline compilation flow. This turned out to be wrong as both webpack and rollup don't have good enough tree-shaking capabilities to do this today. We think that in the future we'll be able to merge these two entry points into one, but we need to give tooling some time before we can do it. In the meantime the reintroduction of the -dynamic package point allows us to separate the compiler dependencies from the rest of the framework. This change undoes the previous breaking change that removed the platform-browser-dynamic package. |
||
|---|---|---|
| .. | ||
| impl | ||
| README.md | ||
| async_route_spec.ts | ||
| auxiliary_route_spec.ts | ||
| bootstrap_spec.ts | ||
| lifecycle_hook_spec.ts | ||
| navigation_spec.ts | ||
| redirect_route_spec.ts | ||
| router_link_spec.ts | ||
| sync_route_spec.ts | ||
| util.ts | ||
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.