Elina

@siku2, I don't think we should add this. Every time I used this in another router (react and angular), it gave me nothing but trouble. The callback to check if...

I'm afraid it isn't as simple as what you describe. As I said in my previous comment, this will need async support to be practically usable. I can't think of...

Now that #1748 is merged, we have main 2 areas to improve on: 1. Use `console.warn` in debug mode to display warnings in browser console. This can be a temporary...

I've been thinking about this and it seems that we would need to have a `Default` requirement for anything that can be extended. > ``` > #[props_extend(button)] // now ButtonProps...

@Follpvosten, after implementing inheritance, I agree with you. The problem I see with catch-all prop (a special `rest` prop?) is that you lose type checking at compile time. The `html!`...

[`material-yew`](https://github.com/hamza1311/material-yew/) is good starting point. It won't compile with master Yew but the interoperability code should be the same.

I've removed `imperative_ref` from 0.20. Also see: https://github.com/yewstack/yew/pull/2783#pullrequestreview-1045277050

> I think the mammoth part is porting the `mdx` format. Docusaurus allows one to embed and _use_ react components written directly in the docs. It would be incredible (in...

> What is the `if` statement syntax you're referring to? ```rust html! { { if condition { something } else { html! {} } } } ``` there's no equivalent...

> Going back to the proposal: > > ``` > for val in range { > { val } > } > ``` > > The user may want to...