fix(location-strategy): crash on going back with router-outlet after closing modal #1748
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.
Modify location-strategy to better handle
<router-outlets>and modal views:_beginModalNavigationmethod shouldn't setcurrentOutletto null when no outlet for the given Frame found.clearOutletmethod: Do not remove outlet, from outlets collection, who belongs to<router-outlet>since it doesn't have any frames[]findOutletmethod should always respect the current_modalNavigationDepthwhen searching for outlet, since there could be 2 or more identical outlets on different modal views ( primary-> (modal:primary)->(modal2->primary))make
findOutletByModalprivate, since it won't be used outside location-strategy anymoreFix #1735