diff options
| author | tv <tv@krebsco.de> | 2026-11-15 20:23:20 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-15 20:23:20 +0000 |
| commit | 6a587c31bfc1c7b21fad0bc7a01af2355a4fa3aa (patch) | |
| tree | 17a384e5c51231e3160d81dc63c0a0c771c90517 /src/document/meta.rs | |
| parent | c96470e4a28f69a640812998b8226faa52bc8d38 (diff) | |
store: one reading of the policy's place
Whether values are ordered by `seq` (`signs_values`) read the policy's
place itself, the first value alone and a map by Automerge's choice of
each field, while the policy as judged (`policy::of`) read it through
the store, which orders by `seq` only where `signs_values` says so, and
merges every map there. They parted: a signed policy that isn't strict
beside a newer plain one that is read as not strict for the one and
strict for the other, and two maps, the newer without the field asking
for signed values, the other way round.
`signs_values` now asks `policy::of`, and the store orders the policy's
own place by `seq` wherever any value there asks for signed values, and
what is within the policy as written, so the two are one reading.
Asked from within that reading, it answers false rather than ask again.
Diffstat (limited to 'src/document/meta.rs')
0 files changed, 0 insertions, 0 deletions
