-
Notifications
You must be signed in to change notification settings - Fork 169
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
Router: support multiple routes for the same component #2741
Comments
How would |
This question was already discussed in the scope of the old Router API. I guess, the conclusions are quite relevant still: #1476 |
I'd suggest introducing something like a repeatable URL generation would thus always be based on |
There could be an additional parameter |
The last comment justifies the reason of having |
What happens if the route target is meant to support wildcard parameters but only on some URL patterns? E.g given a route target like this, I want Flow to match the context root and
|
@sayo-vaadin A navigation target has one route and 0 - n aliases. If you want to make different aliases work in different ways, then you'd probably have to define those as distinct navigation targets that just happen to use the same contents. |
remove the workaround for the Flow issue vaadin/flow#2741 that was added in the PR #210 Jira: BFF-352
…299) remove the workaround for the Flow issue vaadin/flow#2741 that was added in the PR #210 Jira: BFF-352
When defining a routes map of an application, as a developer, I want to define multiple routes for some views (e.g. both
/
and/storefront
should be handled by the same view).With the new Router API that is not supported at the moment (flow-1.0.0.alpha6).
A workaround exists:
The text was updated successfully, but these errors were encountered: