Simon

> Do you think it could be possible to put some guidance either in the docs or with an example? Let's open a new issue for this.

That's something I've wanted for a really long time now. Not only for callbacks but for all kinds of props. I've been thinking about using an approach similar to the...

Yes, it needs a clever idea to make it work with the `html!` macro though, because it is completely unaware of the actual `Properties` struct. One idea I have is...

This point has always been somewhat misleading because Yew makes (almost) no effort in this regard. Interoperability depends on the build system and the bindings library. Nowadays Yew only supports...

> Slight tangent, but React insists on throwing a warning whenever you use a key that is simply the index of the object being displayed. I would suggest we don't...

Having the user explicitly set the `key` prop to remind them of its importance is a good point. I think we should discuss how we want to go about doing...

This should be possible using `proc_macro_diagnostics` which are still unstable. We could abort with an error for now and switch to a suppressible lint error in the future

Thanks for providing your stance on this, @allan2. The following might be a bit direct for which I do apologize, but I wanted to get straight to the point. >...

Can you try applying the `wasm_bindgen(start)` attribute to the main function to see whether that causes wasm-bindgen to insert the instantiation code: Also, it would be great to have the...

Sadly Rust doesn't provide a way for macros to format the code they're given. The only option right now is to format the code by hand. For the Rust code...