What's the MVP that's shippable to hex.pm

Not so much what we need to support - but ideas that have come to mind since I have actually been poking around and have it running.

Still familiarizing myself with the macro stuff - will need to collaborate more on this for sure. #1

[ ] Iron out use cases where data is shared between live_data servers(users).
- For example, a postgres table, being accessed via live_data. How does a row change get propagated to the other connected users viewing that table? #3
[ ] Testing
- could possibly leverage similar mechanism for testing a raw channel - have not really looked into it
[ ] Built in persistence?
- Would be interesting to expose an API/option that automatically persists state to an ets table or something, for things like view/session state that that do not belong in a DB, but could persist between page refreshes/disconnecting/reconnecting to the channel.
- Another idea would be allowing the client to periodically persist state, and when re(connecting) they provide an initial state that is passed to the server when joining the channel (am currently using a similar idea to avoid a loading state, could be expanded upon by passing the clients suggested default state to the server.
- This could also be used to persist a users live_data ID - generating once when first loading the app - and then storing that in localstorage or whatever for the next time they connect to the page - keeping the component UUIDs more stable between page loads.
[x] erlang cluster capability
- registering the processes via {:global, "name"} might be enough, this is a change I made - seems to work OK.

[ ] typescript
[ ] error/connection handling (should just need to wrap logic exposed from core package)

Lots of documented examples both simple and more complex of how this can be used. Probably just react until interest in some other framework emerges.

surferseo / live_data