Routing by convention question

[nbljsph]

Hello all,
I've spent all of 12 hours collectively learning about rust and yew, as I'm trying to get a handle on web assembly (so if this question has already been asked/answered my apologies, I couldn't find it in GitHub or the docs easily.

I'm trying to see if I can setup routing by convention for pages similar so what you would see in Vue or .NET razor pages where there's a base "pages" folder and each sub folder and named file becomes a route without having to setup a routing table directly, or even if there could be an attribute or trait you place in the page.rs which could define routes with the page rather than have one file. Is that something that exists currently?

[teymour-aldridge]

I think the router is what you want.

API docs: https://docs.rs/yew-router/0.14.0/yew_router/
Docs: https://yew.rs/docs/en/concepts/router
An example: https://github.com/yewstack/yew/tree/master/examples/router

[teymour-aldridge]

Oh right; I don't think such a thing exists at this time (the router is all that I'm aware of).

I imagine it would also be trickier to achieve with Rust than would be with e.g. Angular which has its own source-to-source compiler.

[allan2]

@nbljsph I believe in Vue, you still have to specify the routes using the standard router.

I think you're looking for a filesystem-based router. I don't know of anything like that in the Rust web ecosystem either, at least not right now.

[nbljsph]

Theirs a spa framework called Nuxt that can do it dynamically in Vue based on file names and I think decorators? But that does answer the question, how difficult do you think it would be to add something like that on top of yew?

[allan2]

My discussion #1821 is somewhat relevant.

Nuxt (Vue) uses an opinionated filesystem router like Next (React). No clue how hard it would be or whether it would be worth doing.

[nbljsph]

I could see wider adoption of this, or at least I could make a case for it where I work based on optimization if it had similar features to other spa frameworks, I might take a crack at it if I can find the spare time, would give me an excuse to get deeper into rust. The closest wasm alternative I've seen is Microsoft's Blazor but the output is just too dang large and slow right now for my liking.