You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Previously, Data was managed separately from StateCtx, which caused several issues:
- No way to pass in-memory-only data (e.g. API request/response bodies). Storing them was odd, but passing into flows wasn’t possible either.
- All commands operated on states except `load` and `store` for Data → inconsistent API.
- Each flow in a chain had to fetch Data separately, making StateCtx useless as a runtime context.
- Data can be heavy compared to State, requiring lazy loading, which was hard to fit into the old interface.
This change unifies Data handling inside StateCtx and makes the design cleaner.
- Data is part of StateCtx via Datas property
- Data could be passed with StateCtx completly in-meory
- Data could be (lazy-)loaded. If the rev of loaded Data match requested we do not load
- Data could be (lazy-)stored. If the data was previously stored and has a checksum and it match the current one we do not store.
0 commit comments