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
We (working with a fortune 100) have started using SvelteKit for a project and the experience so far has been very good, but as the project growing big, we're finding that those +page.. files are coming out as kind of an eye sore, esp since many people have started working on this project. Although we tried hard to adjust (setting label format to 'medium' in Vscode also not helping to be honest) but its just keep getting in the way of otherwise an amazing developer experience.
Having a configuration to map 'routes + methods' to the corresponding 'file/modules/functions' would give flexibility for developers to chose files/modules at their discretion.
The syntax & semantics could be completely different, but the gist is something as follows
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We (working with a fortune 100) have started using SvelteKit for a project and the experience so far has been very good, but as the project growing big, we're finding that those +page.. files are coming out as kind of an eye sore, esp since many people have started working on this project. Although we tried hard to adjust (setting label format to 'medium' in Vscode also not helping to be honest) but its just keep getting in the way of otherwise an amazing developer experience.
I'm not sure if this has been discussed (and dismissed), but can we explore to have a routing based on config file, something similar to what Django (https://www.django-rest-framework.org/api-guide/routers/) or https://javalin.io/documentation#endpoint-handlers does.
Having a configuration to map 'routes + methods' to the corresponding 'file/modules/functions' would give flexibility for developers to chose files/modules at their discretion.
The syntax & semantics could be completely different, but the gist is something as follows
addRoute('/foo/bar', {'page':'/site/bar.js', .....});
This could be completely optional to the exiting directory based routing.
Or am I missing something?
Beta Was this translation helpful? Give feedback.
All reactions