b602bd8c83
closes https://github.com/angular/angular/issues/4943 BREAKING CHANGE: `Location` and other related providers have been moved out of `router` and into `platform/common`. `BrowserPlatformLocation` is not meant to be used directly however advanced configurations may use it via the following import change. Before: ``` import { PlatformLocation, Location, LocationStrategy, HashLocationStrategy, PathLocationStrategy, APP_BASE_HREF} from 'angular2/router'; import {BrowserPlatformLocation} from 'angular2/src/router/location/browser_platform_location'; ``` After: ``` import { PlatformLocation, Location, LocationStrategy, HashLocationStrategy, PathLocationStrategy, APP_BASE_HREF} from 'angular2/platform/common'; import {BrowserPlatformLocation} from 'angular2/src/platform/browser/location/browser_platform_location'; ``` Closes #7962 |
||
---|---|---|
.. | ||
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
.