Hi everyone,

We just released v0.3.0 of LiveStash. This update brings two heavy-lifting features for distributed apps and better DX:

• Redis Adapter: State lives securely in Redis, while the browser only holds a lightweight reference.
• Opt-in Automatic Stashing: LiveStash detects changes in stashed assigns and updates them automatically (no need for explicit stash/1 calls anymore).

If you have any questions feel free to reply here, create an issue, or start a new thread on GitHub discussions.

Hi everyone,

I’m happy to share that today we released LiveStash v0.2.0!

We took your feedback to heart and we’re excited to introduce the suggested improvements. This version introduces breaking changes to our main stash API, with the goal of making it simpler, more declarative, and more fault-tolerant.

Here is what is new and changed in v0.2.0:

• Declarative assigns API (Breaking): We removed stash_assigns/2 in favor of stash/1. Assigns that should be persisted must now be declared directly in the use macro options.

• TTL unit update (Breaking): Changed the TTL configuration to use seconds instead of milliseconds.

• Configuration validation: We added validation for user config to improve API correctness and fail fast on invalid inputs.

If you have any questions, ideas, or bug reports, feel free to reply here, create an issue, or start a new thread on GitHub discussions. Let us know how the new API feels!

I’ve tried something similar before, however, I am concerned that there could be possible race condition between save and restore, thus perpetual a corrupt state. The client could reconnect so fast, and spin up a new Liveview process before the old one was killed. So, for a brief moment, you could have 2 LV processes, representing the same session, even from the same browser tab.