Greg Johnston

Was putting together this example and got distracted. Rather than using `children` just pass things as normal props. Here is an example that supports either dynamic or not. ```rust #[component]...

Just to expand a little for anyone reading this in the future... This is a genuine drawback of fine-grained reactive UI relative to something like a virtual DOM — Since...

> I don't quite understand what the NotRawCallback trait is trying prevent me from doing; presumably it's to prevent me shooting myself in the foot and maybe what I'm trying...

@bicarlsen For this particular example (and similar examples), using `Callback::new()` instead of `Callback::from()` is fine. It's just the `From` implementation that is broken.

Thanks. This is somewhat awkward as it's a breaking change. I think the `` change is unlikely to affect many use cases, but the comment one may be more widely...

See also #1284, as there's a lot of overlap here. To be clear: the reactive system *does* run on the server. `create_effect` does not, but `create_isomorphic_effect` does. (This isn't the...

I don't know the first thing about how rust-analyzer works. Is there a reason to think this was an intentional decision by rust-analyzer, not a bug/regression? If it was an...

The warning here will just need to be updated so that it is disabled in user effects -- you are correct that there is no actual issue, it's a false...

This doesn't warn on 0.7/current git main, so I'll go ahead and close this issue. 0.7 also supports top-level resource reads without explicit suspense pretty well, so for example this...

That is the expected behavior of ``, yes. It's described more explicitly in [the description in the book](https://book.leptos.dev/view/06_control_flow.html#show). The Show component is extremely straightforward: here's the complete body of the...