Add support for route handling without requiring a `Component`

At the moment, in order to handle navigation to a particular route by forwarding to one of several views depending on a certain condition, one needs to create a dummy Component and either annotate that with @Route, or use RouteConfiguration.setRoute(...) which also requires a Class<? extends Component>. Since there is no actual view that should be shown for this route, it shouldn’t be necessary to create a dummy component class which will also get instantiated at runtime.

Consider support for registering a route with custom navigation handling that doesn’t require a UI component.

[Legioth]

On a conceptual level, what this might mean is that there are actions registered for different URL patterns. There are terminal actions such as rendering a component inside a parent layout, showing an error or doing an external redirect, as well as intermediate actions that just conditionally delegate to some other action or URL.

[HermanBovens]

That is indeed my use case: handling A URL and, depending on user’s permissions, forward/redirect to a specific route. Using a dummy Component works, but feels like a workaround.

Op ma 10 mei 2021 08:25 schreef Pekka Hyvönen @.***>:

Ok @HermanBovens https://github.com/HermanBovens - can you please provide more details on the use case you have and how this solves that ?

I would just use a dummy component for the registered route and then either forward to the correct route component to be showed or just add the correct component as the child component.

I’m speculating, but I guess what you’d want to do (?) is register some handler that is invoked for a certain route path and then it forwards to another route instead. Like for example a class with Route and implements a one method interface where it gets routing data and a callback to call to make the forward/redirect - which will give the router the component(s) that should be actually shown. And in case the callback is not invoked, then the 404 error page would be shown.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/vaadin/flow/issues/10419#issuecomment-836239167, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOVHA2RDDZNUC7EVCSMNTLTM5363ANCNFSM4ZZUSZEA .