Permalink
Switch branches/tags
Commits on Oct 17, 2018
  1. feat(router): add prioritizedGuardValue operator optimization and all…

    jasonaden authored and mhevery committed Oct 15, 2018
    …owing UrlTree return from guard (#26478)
    
    * If all guards return `true`, operator returns `true`
    * `false` and `UrlTree` are now both valid returns from a guard
    * Both these values wait for higher priority guards to resolve
    * Highest priority `false` or `UrlTree` value will be returned
    
    PR Close #26478
Commits on Oct 15, 2018
  1. fix(router): fix regression where navigateByUrl promise didn't resolv…

    jasonaden authored and mhevery committed Oct 15, 2018
    …e on CanLoad failure (#26455)
    
    Fixes #26284
    
    PR Close #26455
Commits on Oct 10, 2018
  1. release: cut the v7.0.0-rc.1 release

    jasonaden committed Oct 10, 2018
  2. Revert "fix(upgrade): properly destroy upgraded component elements an…

    jasonaden committed Oct 10, 2018
    …d descendants (#26209)"
    
    This reverts commit 912f3d1. Revert is needed due to compilation failures due to this PR inside Google.
  3. docs: release notes for the v release

    jasonaden committed Oct 10, 2018
Commits on Oct 8, 2018
  1. Revert "fix(upgrade): properly destroy upgraded component elements an…

    jasonaden committed Oct 8, 2018
    …d descendants (#26209)"
    
    This reverts commit 5a31bde.
Commits on Oct 4, 2018
  1. refactor(router): get guards only one time and simplify guard operato…

    jasonaden committed Oct 3, 2018
    …r signature (#26239)
    
    PR Close #26239
  2. refactor(router): convert PreActivation's resolve data to pure functi…

    jasonaden committed Oct 2, 2018
    …ons & remove PreActivation class (#26239)
    
    PR Close #26239
Commits on Sep 27, 2018
  1. refactor(router): cleanup to navigation stream for readability and do…

    jasonaden authored and alxhub committed Sep 17, 2018
    …cumentation (#25740)
    
    * Pull out `activateRoutes` into new operator
    * Add `asyncTap` operator
    * Use `asyncTap` operator for router hooks and remove corresponding abstracted operators
    * Clean up formatting
    * Minor performance improvements
    
    PR Close #25740
  2. refactor(router): update test based on router quick-cancelling ongoin…

    jasonaden authored and alxhub committed Sep 12, 2018
    …g navigations (#25740)
    
    PR Close #25740
  3. refactor(router): move routing into a single Observable stream (#25740)

    jasonaden authored and alxhub committed Aug 15, 2018
    This is a major refactor of how the router previously worked. There are a couple major advantages of this refactor, and future work will be built on top of it.
    
    First, we will no longer have multiple navigations running at the same time. Previously, a new navigation wouldn't cause the old navigation to be cancelled and cleaned up. Instead, multiple navigations could be going at once, and we imperatively checked that we were operating on the most current `router.navigationId` as we progressed through the Observable streams. This had some major faults, the biggest of which was async races where an ongoing async action could result in a redirect once the async action completed, but there was no way to guarantee there weren't also other redirects that would be queued up by other async actions. After this refactor, there's a single Observable stream that will get cleaned up each time a new navigation is requested.
    
    Additionally, the individual pieces of routing have been pulled out into their own operators. While this was needed in order to create one continuous stream, it also will allow future improvements to the testing APIs as things such as Guards or Resolvers should now be able to be tested in much more isolation.
    
    * Add the new `router.transitions` observable of the new `NavigationTransition` type to contain the transition information
    * Update `router.navigations` to pipe off of `router.transitions`
    * Re-write navigation Observable flow to a single configured stream
    * Refactor `switchMap` instead of the previous `mergeMap` to ensure new navigations cause a cancellation and cleanup of already running navigations
    * Wire in existing error and cancellation logic so cancellation matches previous behavior
    
    PR Close #25740
Commits on Sep 21, 2018
  1. refactor(router): cleanup to navigation stream for readability and do…

    jasonaden authored and kara committed Sep 17, 2018
    …cumentation (#25740)
    
    * Pull out `activateRoutes` into new operator
    * Add `asyncTap` operator
    * Use `asyncTap` operator for router hooks and remove corresponding abstracted operators
    * Clean up formatting
    * Minor performance improvements
    
    PR Close #25740
  2. refactor(router): update test based on router quick-cancelling ongoin…

    jasonaden authored and kara committed Sep 12, 2018
    …g navigations (#25740)
    
    PR Close #25740
  3. refactor(router): move routing into a single Observable stream (#25740)

    jasonaden authored and kara committed Aug 15, 2018
    This is a major refactor of how the router previously worked. There are a couple major advantages of this refactor, and future work will be built on top of it.
    
    First, we will no longer have multiple navigations running at the same time. Previously, a new navigation wouldn't cause the old navigation to be cancelled and cleaned up. Instead, multiple navigations could be going at once, and we imperatively checked that we were operating on the most current `router.navigationId` as we progressed through the Observable streams. This had some major faults, the biggest of which was async races where an ongoing async action could result in a redirect once the async action completed, but there was no way to guarantee there weren't also other redirects that would be queued up by other async actions. After this refactor, there's a single Observable stream that will get cleaned up each time a new navigation is requested.
    
    Additionally, the individual pieces of routing have been pulled out into their own operators. While this was needed in order to create one continuous stream, it also will allow future improvements to the testing APIs as things such as Guards or Resolvers should now be able to be tested in much more isolation.
    
    * Add the new `router.transitions` observable of the new `NavigationTransition` type to contain the transition information
    * Update `router.navigations` to pipe off of `router.transitions`
    * Re-write navigation Observable flow to a single configured stream
    * Refactor `switchMap` instead of the previous `mergeMap` to ensure new navigations cause a cancellation and cleanup of already running navigations
    * Wire in existing error and cancellation logic so cancellation matches previous behavior
    
    PR Close #25740
Commits on Sep 11, 2018
  1. docs(bazel): add info on options for nodejs_test rule (#25877)

    jasonaden authored and IgorMinar committed Sep 9, 2018
    PR Close #25877
Commits on Aug 22, 2018
  1. release: cut the v7.0.0-beta.3 release

    jasonaden committed Aug 22, 2018
  2. docs: release notes for the v6.1.4 release

    jasonaden committed Aug 22, 2018