feat(router): Execute RunGuardsAndResolvers function in injection context#64938
Merged
Conversation
8f055fd to
82888f8
Compare
…text Allows more sophisticated checks based on information available in DI (e.g. the router state). Use-cases have been described in angular#53944 / angular#31843 (comment) resolves angular#53944
82888f8 to
7f22b66
Compare
This eliminates the need to pass around the EnvironmentInjector everywhere we need the injection context for a route.
7f22b66 to
22664ce
Compare
Contributor
Author
14 tasks
Contributor
|
This PR was merged into the repository. The changes were merged into the following branches:
|
|
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.
3 participants
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.
Allows more sophisticated checks based on information available in DI
(e.g. the router state). Use-cases have been described in #53944 / #31843 (comment)
resolves #53944