-
-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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: use outlet directly if route without element #8497
Conversation
Can you add a test to go with this? |
Ok, I will add test later. |
9bee998
to
16e60be
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. Not sure if this needs MJ/RF's approval, but I went ahead and requested it anyways.
Hey @timdorr, any chances to get that PR merged? I have the same issue with the Outlet context & nested route without the |
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.
Approved! (Seriously though, tested, works, and this is exactly what we need)
Just found this, and this is the fix I need! Nested routes are quite useless to me without this. Would be great if you could merge it as soon as possible, thanks! |
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.
Looks good, and thank you for the tests! We just need to fix up the PR title before merging.
1cf7fb2
to
70d3bf5
Compare
Looks like it's good now. Thanks! |
Fix #8492