Thanks, I suppose I’m a bit confused as to how to deal with state now that there are 3 things all trying to work together (unpoly view state, phoenix controllers, phoenix sockets). In the above example I am starting with the controller’s assign state and then updating the assign “live” via the socket, however the controller doesn’t know anything about that and if unpoly asks the controller for something else it doesn’t have the updated state. Maybe authentication is a bad first use case to learn about unpoly + drab… leaves me wanting some examples to see what patterns work and how you are thinking about state with these tools?
Maybe this should be forked into a new topic?
