Skip to content

[Bug] Using <router-link> to a child or sibling application should work on isolated run #5

@davidmeirlevy

Description

@davidmeirlevy

When you run the full solution:
-host app

    • child app 1
      • <router-link :to={name:"childApp2Route"}>link</router-link>
    • child app 2

this use-case will work when you run the child app from the host app because the child plugin will enrich the router of the child app with the routes of its sibling.

Although, when you're trying to run the child app directly from the browser, it doesn't have those routes, so vue router will throw exceptions.

Suggested solutions:

  1. Define other siblings' routes specifically. very strict, but less convenient to the user.
  2. Create a MicrofRouterLink component that is less strict (somehow seems very dangerous to me, and needs to be able to debug the routes).

If you have any new suggestions, please comment here or commit a PR.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions