Multiple (nested) router instances

[vlukashov]

As a developer I want to create route components that handle their own routing independently from the other parts of the app so that there is no need for any kind of central coordination more than agreeing on URL prefixes for different components.

As a component developer I want to be able to use Vaadin.Router in my route component independently from any other routing solution(s) used in the other parts of the app.

The first use case is already addressed by #28 (by having a single Vaadin.Router instance and loading child route configs dynamically, per-component). The second use case requires special support for creating multiple instances of Vaadin.Router and ensuring that they work well together.

DoD:

• the routes defined in a nested Vaadin.Router instance are rendered in the same resolve pass as root route component, i.e. the order of calling lifecycle callbacks is the same as if all routes were defined on the same router instance.
• if a route in a nested VaadinRouter instance prevents a transition, the outer router also stops the resolve pass
• if a route in an outer Vaadin.Router instance redirects navigation, the inner router would not even start with processing the navigation event.
• there is a demo of using nested Vaadin.Router instances

The common DoD applies.

[gitawego]

It's a must have feature :)

We are building a webapp using vaadin router, and we don't want to use shadow dom because of the theming issue, but currently the nested components feature is based on slot, which makes it a dead end for us.

[vlukashov]

Thanks for sharing the details behind why you need this. It sounds like adding support for light DOM parent layouts would also be an acceptable solution.

Using Vaadin Router without Shadow DOM is something several other users have requested here and there. Your comment adds another voice to that.

[joezappie]

Any further work on this? I too am looking for this exact same thing - ability for components to define their own routes.