You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Interface wise I would say it makes sense to simply default to this behavior if component isn't specified.
Also, I don't know if it's the same or another issue, but name hierarchies would make this feature quite powerful
The text was updated successfully, but these errors were encountered:
Hello, thank you for taking time filling this issue!
However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).
I hope to see your helper-created issue very soon!
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.
Interface wise I would say it makes sense to simply default to this behavior if
component
isn't specified.Also, I don't know if it's the same or another issue, but
name
hierarchies would make this feature quite powerfulThe text was updated successfully, but these errors were encountered: