Router rewrite

[hamza1311]

i was playing around with writing a SPA router and ended up with a working Yew router with this API:

#[function_component(Main)]
fn app() -> Html {
    let onclick1 = Callback::from(|_| RouterService::push("/no/2"));

    let onclick2 = Callback::from(|_| RouterService::push("/"));
    let _current_route = RouterService::current_route();

    html! {
        <Router>
            <Route to="/">
                <h1>{"Hello World"}</h1>
                <button onclick=onclick1>{"Click me no"}</button>
            </Route>
            <Route to="/no/:id">
                <h1>{"Forbidden"}</h1>
                <button onclick=onclick2>{"Click me home"}</button>
            </Route>
            <Route to="/404">
                <h1>{"404"}</h1>
            </Route>
        </Router>
    }
}

I find it an improvement over the current router design in a few ways

• No need for a RouterAgentDispatacher
• No stateful RouterService
• Easier to get the current route and the parameters passed in its url
  No need to pass everything down as props
• Easier to navigate between pages without using a RouterAnchor (or similar)
• The routes are order independent

However, this API has one downside: the routes are stringly typed instead of being an enum. There are some workarounds to this (like storing route string in consts and using those) though.

Thoughts on this design?

---

I will be making a PR where we can discuss (and improve on) the implementation details.

[hamza1311]

I created the PR (#1791).