CommitOptions.expectRevision Contract 2.0.0 · package sha256
a857eca95b35921109faf997094bb4192f12527d9d0fcd4be7e97f06425bad6e· generated fromconfigurator-runtime.d.tsbyservices/onsite-scripter/scripts/build-contract-docs.mjs; edit the source, not this file.
Property of CommitOptions · inherited by WriteOptions, TransactionOptions · stable · since 2.0.0
expectRevision?: number;If-match on session.revision. A mismatch refuses the write ('refused', reason 'conflict');
nothing runs. While a transaction is open or queued ahead of it, or while a recorded write
ahead of it in the write queue is pending, it is refused 'busy' at once. Behind pending
look-only writes alone (apply, Collection.set, stage.set) it waits its turn: those never
move revision. It waits behind a dry run too, a write or a transaction with dryRun: true,
open or queued: a dry run never moves revision (spec section 6.1, O2e).
Default: undefined (no check)
| Rule | Result |
|---|---|
| 1. Neutral name | pass: expectRevision names no product |
| 2. A precedent | not recorded: no ledger row (coverage.json) names this member or its owner |
| 3. Two apps, or labs | not recorded: no ledger row names this member or its owner |
| 4. The cheaper fix first | not recorded per member (Appendix B decides it per need) |