WorldSEnder

The `css!` macro implements a DSL for css, and so it does not expect arbitrary expressions in the place of the string literal (the latter can be parsed at compile...

You are correct, there is currently no up-to-date version for yew's `master` branch. IF it existed, it will get updated in this PR: #69 though, but I currently don't have...

Yes, this is supported. E.g. in a styled component ```rust, css let hover_class = css!( :hover { color: blue; } ); ``` You can think of all selectors in a...

Can you give a short description what you are trying to achieve and which pseudo class you would like to see, so I can provide a tailored example?

> Consider this struct: > > ```rust > struct UseStateHandle Under what kind of circumstances, would one of the public built-in hook want to return &T than Rc (or one...

> If you have a `UseStateHandle`. If you in turn pass this as an event listener, then `Html` will also need to be `Html

Quick further update: I'm trying out error cases, and the rust compiler sometimes is really determined to trace the error back to the implicit `_ctx` attribute and `'hook` lifetime which...

Thanks for the PR. Since I think none of the maintainers speak Portuguese, reviewing will probably take time. Still, keeping the PR open will keep it discoverable and to anybody...

I can see callback refs slowly appearing on the horizon, specifically with #2551 and #2567

Negative literals are [not literals but expressions](https://users.rust-lang.org/t/why-are-negative-value-literals-expressions/43333), so the (pedantic) error is correct to the letter. But I agree that we could allow this case [in the macro parser](https://github.com/yewstack/yew/blob/master/packages/yew-macro/src/props/prop.rs#L101-L109). I...