Skip to content

Allow nested routes without parent component #3156

Open
@ghost

Description

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 powerful

What 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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    feature requestfixed on 4.xThis issue has been already fixed on the v4 but exists in v3

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions