Change the way that folder-contained routes are discovered / resolved

[GGAlanSmithee]

Feature request

Change the way that folder-contained routes are discovered / resolved

Describe the solution you'd like

Instead of having sapper look for routes/{route}/index.svelte, have it look for routes/{route}/{route}.svelte (or make both patterns available)

Describe alternatives you've considered

Non really.

How important is this feature to you?

It's not super important, but as a project grows having a bunch of index.svelte is less than ideal from a devx perspective.

Additional context

I understand that the current implementation is according the default NodeJS file resolving algorithm, but having worked at large nodejs projects, it does not scale with project size.

This is a breaking change, since it would dissalow {url}/{route}/{route} but IMO that's a worthwhile tradeoff.

[mrkishi]

I'm not sure I understand. What kind of routes would you want to have?

Currently, routes/[route].svelte is synonymous with routes/[route]/index.svelte.

[GGAlanSmithee]

@mrkishi

I would like routes/[route]/index.svelte to instead be routes/[route]/[route].svelte to avoid having a lot of ambiguous (as in hard to navigate in an IDE) index files

[khrome83]

At that point, why don’t you use - `routes/[route].svelte`? Just seems there is a solution for this already?

…

--- Zane Milakovic

On Oct 24, 2019, 11:41 AM -0500, Alan Smithee ***@***.***>, wrote: @mrkishi I would like routes/[route]/index.svelte to instead be routes/[route]/[route].svelte to avoid having a lot of ambiguous (as in hard to navigate in an IDE) index files — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[GGAlanSmithee]

For organisation reasons, like blog in the example project and nested routes

[GGAlanSmithee]

to make it more clear:

As an application grows, the # of routes might as well. In a lot of these cases, you might want to co-locate files that are logically coupled, such as with blogs in the example app.

Doing this with the current solution you'll end up with a lot of index.svelte files, like:

routes
	user
		index.svelte
		// more files
	blog
		index.svelte
		// more files
	todo
		index.svelte
		// more files
	recipe
		index.svelte
		// more files

This might seem like a non-issue, but it actually makes it quite hard to navigate between open files in an IDE, VS Code for example. I am speaking from experience of a large react/redux app with a gazillion connect HOCs in dedicated index files though, so this might not be a problem in an idiomatic Sapper app.

[GGAlanSmithee]

Or maybe atleast make it configurable? Would you consider a PR for this?

[mrkishi]

Sorry, I can't really relate to that. However, if something like this were to be included, it'd definitely need a different syntax since as proposed it'd be confusing and ambiguous.

As for solving the issue for now... How about using routes/blog.svelte and routes/blog/{files}?

[GGAlanSmithee]

Ok, yeah that's a great idea!

[GGAlanSmithee]

and this is already supported, awesome. You lose a bit of co-location, but it's a reasonable tradeoff!

This might be implicitly understood but would you like a note regarding this in the docs?