New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(router): Routed components never inherit RouterOutlet
`Environm…
#54265
fix(router): Routed components never inherit RouterOutlet
`Environm…
#54265
Conversation
a70befd
to
887ff89
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
reviewed-for: public-api
bc7afc6
to
79a901c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Reviewed-for: public-api
…entInjector` This commit ensures components in the route config predictably always get their providers from the hierarchy available to routes rather than sometimes being dependent on where they are inserted. fixes angular#53369 BREAKING CHANGE: Providers available to the routed components always come from the injector heirarchy of the routes and never inherit from the `RouterOutlet`. This means that providers available only to the component that defines the `RouterOutlet` will no longer be available to route components in any circumstances. This was already the case whenever routes defined providers, either through lazy loading an `NgModule` or through explicit `providers` on the route config.
…nvironmentInjector`
79a901c
to
217f37a
Compare
caretaker note: Will need to patch this change to tracking_router_outlet when sycning cl/608676576 |
This PR was merged into the repository by commit da906fd. |
…EnvironmentInjector` (angular#54265)" This reverts commit da906fd. This change causes some test failures in google3.
caretaker note: Please merge and sync on its own (and patch the tracking outlet from cl/608676576) |
This PR was merged into the repository by commit 3839cfb. |
…EnvironmentInjector` (angular#54265)" (angular#54895) This reverts commit da906fd. This change causes some test failures in google3. PR Close angular#54895
…entInjector` (angular#54265) This commit ensures components in the route config predictably always get their providers from the hierarchy available to routes rather than sometimes being dependent on where they are inserted. fixes angular#53369 BREAKING CHANGE: Providers available to the routed components always come from the injector heirarchy of the routes and never inherit from the `RouterOutlet`. This means that providers available only to the component that defines the `RouterOutlet` will no longer be available to route components in any circumstances. This was already the case whenever routes defined providers, either through lazy loading an `NgModule` or through explicit `providers` on the route config. PR Close angular#54265
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. |
…entInjector`
This commit ensures components in the route config predictably always get their providers from the hierarchy available to routes rather than sometimes being dependent on where they are inserted.
fixes #53369
BREAKING CHANGE: Providers available to the routed components always come from the injector heirarchy of the routes and never inherit from the
RouterOutlet
. This means that providers available only to the component that defines theRouterOutlet
will no longer be available to route components in any circumstances. This was already the case whenever routes defined providers, either through lazy loading anNgModule
or through explicitproviders
on the route config.