Repository navigation
[feat] Conditional routing #243
Description
My feature request is simple, adding conditional routing. The proposal is to add two properties from the Show component into the RouteDefinition interface.
when: () => booleanfallback: () => JSX.Element | string | Array<JSX.Element | string>
if when is not defined, use a default value that always computes to true. If the computed value of when() is false render fallback() instead of component or element.
In my opinion this allows a much cleaner syntax for creating routes that should only be available when certain conditions are met. If the conditions are not met it offers a simple way to show the end-user that some condition was not met. If fallback is not defined, treat the route as it is a 404.
Activity
fabiospampinato commentedon Mar 12, 2023
In some sense this is doable already by conditionally loading a
<Navigate>component or the actual component for the route.richardeschloss commentedon Jul 17, 2023
I think I have another use case for conditional routing. Suppose you're working on a very large web app with lots of routes. But as a developer a specific feature you want to work on only requires a small subset of those routes to get created. You only want that small subset to be built because you want your initial boot time to be snappy. How can we accomplish this with solidjs router?
Some ideas I had were:
I think 2 is may be more difficult to implement than 1 but any of them may provide faster developer experience.
Perhaps if there was a hook solid-router could give us "updateRoutes" or something we could use in our vite config (or in a vite plugin) that may be ideal since we wouldn't have to mess with the commenting out code in the app. Thoughts?