File based Routing

[itsezc]

With the rise of popularity of meta frameworks Next, Nuxt and SvelteKit, it'd be nice to see a file based router for Yew. I'm aware these are meta frameworks which are built on top of React, Vue and Svelte respectively; given the current circumstances, it'd be great if this was supported out of the box or perhaps the Yew team can investigate the creation of a separate project for a meta framework.

[futursolo]

Unlike JavaScript, there are some complications with file-based routing, imposed by the Rust language.

Consider the following layout:

/pages/
  - home.rs
  - articles/
    - [id].rs

1. Modules (files) are required to be imported via "mod", simply adding a file will not work and requires manual importing.
2. Modules cannot run any code unless it is called by main() and cannot make pub unless its parent declare the module as pub, which means they cannot register themselves as a route automatically.
3. Module name needs to be valid identifier in Rust. We cannot use [id].rs as a module name unless it is referenced with something like #[path = "[id].rs"] mod id;.

I think these limitations above kind of defeats the point of file-based routing unless we have a command line tool to do code generation. However, it still is kind of unintuitive if for each page a command has to be run to do code generation before it can be enabled.

However, just like React / Next.js, file-based routing does not require any first-party support from the core Yew renderer.
So if anyone has any good idea on how to implement this, feel free to create a crate to experiment with it.
I am very keen to see a Next.js-like framework for Yew.

[gedw99]

https://github.com/adhocteam/pushup is a file based router with htmx

its a continuous compile setup..