Story 5 — Widgets read from the store
As a flow builder, I want a widget to read a value from the store instead of waiting for a message, so that my data flow and my presentation flow don't have to be the same flow.
Lets people address the store. A typedInput option alongside msg.payload: choose the store, give it a key, drop the wire. Nothing moves — the store has been in global context since Story 2.
Acceptance criteria
Open questions
- Store-bound widgets and per-client messages — a flow can target one browser with
msg._client.socketId, and those messages bypass the store. A store key holds one value, so a bound widget shows everyone the same thing. Reading from the store is opt-in per widget, so nothing changes by default, but what a bound widget does when a client-scoped message arrives is undecided. Per-client targeting stays.
Story 5 — Widgets read from the store
Lets people address the store. A typedInput option alongside
msg.payload: choose the store, give it a key, drop the wire. Nothing moves — the store has been in global context since Story 2.Acceptance criteria
Open questions
msg._client.socketId, and those messages bypass the store. A store key holds one value, so a bound widget shows everyone the same thing. Reading from the store is opt-in per widget, so nothing changes by default, but what a bound widget does when a client-scoped message arrives is undecided. Per-client targeting stays.