Dynamic loader layout without index

[DaXcess]

I'm trying to write a layout for a dynamic route that does not have an index page, with paths like these:

/session/$sessionId/logs => LogsPageComponent
/session/$sessionId/settings => SettingsPageComponent
/session/$sessionId/search => SearchPageComponent

So this means that:

/session => NotFound
/session/$sessionId => NotFound

I want to write a 'layout' that performs some data fetching at the /session/$sessionId level (as all sub-routes depend on this information), but am not able to figure out how to properly structure my files for this to work properly (Using file-based routing).

First thing I tried to do was make routes like /session/_$sessionId, but this did not seem to work.

Something else I stumbled upon was using paths like /session/$sessionId/_layout/logs.tsx, and then loading the data in /session/$sessionId/_layout.tsx, however this introduces an annoying folder structure (or file structure, by prefixing all filenames with _layout.{}.tsx) where all of the code needs to be in a _layout folder for them to work properly. I've also noticed that now the route /session/$sessionId is no longer throwing a 404 (like I was expecting), but the Outlet (in the __root.tsx) also returns no elements, so no clue what is going on there.

I'm not really sure what else I can try, as I couldn't find any examples that share the same functionality that I'm aiming for. Maybe what I want to achieve simply isn't possible?

[schiller-manuel]

I've also noticed that now the route /session/$sessionId is no longer throwing a 404 (like I was expecting), but the Outlet also returns no elements, so no clue what is going on there.

This sounds like a bug in the router generator. can you please provide a complete minimal example? ideally by forking one of the existing examples

in your case, I would create a /session/$sessionId.tsx as well as an explicit /session/$sessionId/index.tsx.
/session/$sessionId.tsx would contain the data fetching and in /session/$sessionId/index.tsx I would throw a notFound or redirect in its beforeLoad()

[DaXcess]

in your case, I would create a /session/$sessionId.tsx as well as an explicit /session/$sessionId/index.tsx. /session/$sessionId.tsx would contain the data fetching and in /session/$sessionId/index.tsx I would throw a notFound or redirect in its beforeLoad()

Okay, I'll check this one out, cheers!

This sounds like a bug in the router generator. can you please provide a complete minimal example? ideally by forking one of the existing examples

Created a minimal example in DaXcess/router, in the /examples/react/basic-file-based example. Created the same session folder structure as described earlier (with the nested _layout), and same behavior present in this minimal example (/session/<id> does not throw NotFound, but also doesn't render anything).

[natedunn]

hey @schiller-manuel and @DaXcess I am dealing with this right now and I am wondering it has gained any bit of traction since

[schiller-manuel]

@natedunn do we have a GitHub issue for this open already? if not please create one including a reproducer

[natedunn]

I see @DaXcess's repo is now not available. I can throw up an issue/repro if that's something that will won't come back.

[natedunn]

@schiller-manuel After attempting and failing to repro, I have found and resolved the specific issue in my own codebase. Unrelated to this issue as far I can tell.