Great question! For actual errors (socket or channel failures for example) I’m underway with adding support for an error event from LiveState and added an issue to track it here: Error handling · Issue #5 · launchscout/live_state · GitHub. I have an initial implementation, but am not entirely happy with what I came up with and want to rework it a little.
For changeset “errors” (really validation failures) my thought is those belong on state. I put together a CRUD example recently to show how this could work, I need to figure out where to put it. With the amount of subprojects, examples and related things it might be time for a livestate github org. For now, I created an issue so I can remember to do this: CRUD example · Issue #6 · launchscout/live_state · GitHub
