-
-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Allow nested routes without parent component #3156
Comments
Its a bit pointless to have to have this file:
|
You sure this one needs an RFC, @posva ? It seems many people are hitting this issue, considering #2105 is the top result when searching for "vue nested routes without main component". Linking my comment from the original issue: #2105 (comment) |
Do you mean this: https://reach.tech/router/example/embedded-routers |
this is really a feature i am missing in vue router, it looks like, any progress on this or place to reopen this? |
God this feature will my code more readable and maintainable. I agree with @ghost on the design:
|
What problem does this feature solve?
This issue already exist, but was closed: #2105 I do believe it shouldn't have been.
The
PassThrough
solution will most likely do it, but it is a workaround. I do not want to specify every view as a pass through.This should imo. be supported by vue-router directly, making it easier to design ones system as small sub components, allowing each component to know it's own navigation and be loosely coupled.
Also, I don't know if it's the same or another issue, but
name
hierarchies would make this feature quite powerfulWhat does the proposed API look like?
Interface wise I would say it makes sense to simply default to this behavior if
component
isn't specified.The text was updated successfully, but these errors were encountered: