diff options
| author | tv <tv@krebsco.de> | 2026-11-15 16:49:08 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-15 16:49:08 +0000 |
| commit | 90ad9e632520d3bbc22562c0fd4db2584ef2a92c (patch) | |
| tree | 64c48d846b7dabb42d3b6b3f1938a0c299f8ea58 /docs/api.md | |
| parent | f751f411e954001c124afa1e3591d10094df15d7 (diff) | |
store: a signed value chosen by seq is named so
Where the policy asks for signed values, a place's value is chosen by
`seq`, but conflict reports still called the choice `newestWins`, and
the code and the architecture still said "newest" of what a read
shows. A report names it `highestSeq`; the rest says "the one a read
shows".
Diffstat (limited to 'docs/api.md')
| -rw-r--r-- | docs/api.md | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/api.md b/docs/api.md index a839f74..05abf44 100644 --- a/docs/api.md +++ b/docs/api.md @@ -192,7 +192,8 @@ one of another kind (a map written over a list), it is written anew. `?conflicts=true` on a read answers `{"value": …, "conflicts": [...]}`: every place on the way where concurrent values were resolved, with all candidates and which was -selected (`mergedMaps` or `newestWins`). A later write at that path ends the conflict. +selected (`mergedMaps`, `newestWins`, or `highestSeq` for a signed value where the policy +asks for them). A later write at that path ends the conflict. ## Following changes |
