a038bb9ae3
Previously when comparing which of multiple possible routes to choose in an ambiguous case, we looked at the specificity of the target of redirect matches rather than the original match. This meant that if a redirect used a whilecard, but redirected to a target that was a static path, we'd cound the static path's specificity instead of the wildcard. This change stores the specificity of the redirect on the RedirectInstruction. Closes #5933 |
||
|---|---|---|
| .. | ||
| 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.