data-cap: a one-page brief
data-cap gives every piece of application data one owner and one shared status, so every part of the application agrees on what the data is doing.
The problem
Different parts of an application each work out their own idea of whether data is loading, stale or changed. They disagree, and nobody owns the answer.
What it does
Each piece of data is declared once, with the fields and operations that touch it. Every consumer then reads the same up-to-date snapshot, whichever fetching or state library sits underneath.
Why it matters
- Components stop disagreeing about what "loading" or "stale" means.
- It works alongside the fetching and state libraries a team already uses.
- A generated report shows who owns each piece of data and what depends on it.
What it costs
Adopting it means adding the package and declaring one piece of data at a time. It is free, open source software under the MIT licence, and it replaces no existing library.
What could go wrong
- data-cap is pre-1.0. Per VERSIONING.md, a minor release may still change a Stable API before 1.0, so pin accordingly and read the changelog on every minor upgrade.
- Security fixes target the latest 0.x release only, and there is no long-term-support branch before 1.0.
- Ownership is enforced by warning, not by blocking, so a mistake is reported rather than prevented.
What we are asking for
Agree that one feature trials it for a few weeks, then judge from its ownership report whether to extend it.
To judge it yourself: Read the README ยท Run the examples
Print this page or save it as a PDF to share.