You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So I understand you have the same site more or less on different domains, and you would like certain routes to only appear on those Domains. The route definition is just JSON ultimately even though we use components, so it could be conditionally constructed I imagine. Unless I'm misunderstanding the use case.
I guess on the server you want to use the request to determine if the routes should be registered and in the client the current URL in the browser?
Activity
indeyets commentedon Dec 5, 2022
Or should this issue be moved to @solidjs/router instead?
orenelbaum commentedon Dec 5, 2022
Yeah I think that it should be moved to the router
ryansolid commentedon Aug 8, 2023
So I understand you have the same site more or less on different domains, and you would like certain routes to only appear on those Domains. The route definition is just JSON ultimately even though we use components, so it could be conditionally constructed I imagine. Unless I'm misunderstanding the use case.
I guess on the server you want to use the request to determine if the routes should be registered and in the client the current URL in the browser?
indeyets commentedon Aug 8, 2023
Domains might have quite different sets of urls, actually. One case is "search." subdomain which would handle a separate set of "pages"
I talk about generic ability to match over domains in addition to the current ability of matching over paths