[2.x only] fix(router): do not finish bootstrap until all the routes are resolved#14327
Merged
Merged
Conversation
259d2f2 to
419fd64
Compare
e9b355a to
1d1f10f
Compare
1d1f10f to
41dd62c
Compare
baae06b to
059085b
Compare
mhevery
approved these changes
Feb 9, 2017
Contributor
|
@vsavkin looks like this pr introduced a bug with |
This was referenced Feb 22, 2017
vicb
added a commit
to vicb/angular
that referenced
this pull request
Feb 23, 2017
… resolved (angular#14327)" This reverts commit 541de26.
IgorMinar
pushed a commit
that referenced
this pull request
Feb 27, 2017
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #12162
This is fix for the 2.x version.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x")
What is the current behavior? (You can also link to an open issue here)
What is the new behavior?
Does this PR introduce a breaking change? (check one with "x")
If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information: