Post #2002378

@m I'd say it's probably individual, but the things that blocked me were: You can create your own hooks, and IMO should do so. Instead of doing use_context::>() make a function that abstracts thisCreate structs for actions that live alongside data. To continue in the same vein as 'current user'. A SessionManager or something that handles: a signal of Option, has a login and logout method etc...Do really really read through the dioxus guide books, there is a lot mentioned there that is IMO missing from the docs wrt. to 'how things are meant to be used'If you're touching it with Signals, you should always triple check whether what your sending around is Clone. A lot of the time, the error messages suck due to a method being impl'd only when T: Clone Read and re-read the RSX docs/guide, lots of good info!Understand the server/ distinctionHave an api module where all your server functions live, which makes it easy to keep the two worlds apart I'm sure there's more, but I feel these have unlocked a lot of the random walls I've hit