Modals with URLS

[NeilWkz]

How do you do this with tanstack router?

Our platform team recently migrated my company onto Tanstack; thanks to the community, it's been really nice to use so far.
I'll describe the behaviour that I've been tasked with executing:
I'm doing an adaptive render that would render a full mobile page with a URL, and on desktop we render a full page with content in a modal overlay. The adaptive render part is no problem.
I know how i would execute the modal with a URL pattern with react-router but I'm struggling to work out from the docs how I would execute this with Tanstack. I know in Next this behaviour is called Parallel Routes and there is a documentation page with that name here on tanstack, but it has a TODO.

Does anyone have any examples of how to execute this pattern in Tanstack? Anything at all for a starting point would be gratefully recieved; sandboxes, links to other repos.

[NeilWkz]

How do you do this with tanstack router?

Our platform team recently migrated my company onto Tanstack; thanks to the community, it's been really nice to use so far.
I'll describe the behaviour that I've been tasked with executing:
I'm doing an adaptive render that would render a full mobile page with a URL, and on desktop we render a full page with content in a modal overlay. The adaptive render part is no problem.
I know how i would execute the modal with a URL pattern with react-router but I'm struggling to work out from the docs how I would execute this with Tanstack. I know in Next this behaviour is called Parallel Routes and there is a documentation page with that name here on tanstack, but it has a TODO.

Does anyone have any examples of how to execute this pattern in Tanstack? Anything at all for a starting point would be gratefully recieved; sandboxes, links to other repos.

No updates here so I'm just bumping to keep alive. If I get some examples I am happy to write some docs and open a pr

[ssatriya]

Why not go with the query param for the time being? I actually tried tanstack start and thought about using search param for now.

[NeilWkz]

Google won't crawl a query param as a separate page because the meta data in the head, canonical URL won't change when a query string changes. It wont be searchable. So it was not fit for our requirements. If you don't need the page to be searchable or it's not information with SEO value then it may work for you

[ssatriya]

Ah I see, thanks for the answer.

[tannerlinsley]

Google will crawl any link it finds unless you tell it not to (many ways to do this), including urls with query/search params. It’s important to use canonical urls (which can include search params) to identify unique pages/content.

We plan on supporting parallel route soon and they will most definitely use search params to track the state of non primary slots.

[NeilWkz]

Thanks Tanner, glad to hear parallel route support is in the works.

Yes trade offs, Adding a mechanism to change the canonical URL for the querystring was more complicated for us so it was easier to comprise the ui. YMMV etc