JsonPatchOp ​

Contract 2.0.0 · package sha256 a857eca95b35921109faf997094bb4192f12527d9d0fcd4be7e97f06425bad6e · generated from configurator-runtime.d.ts by services/onsite-scripter/scripts/build-contract-docs.mjs; edit the source, not this file.

Type · import type { JsonPatchOp } from '@holostep-configurators/runtime-client/contract'; · stable · since 2.0.0 · section 5. Writers, transactions, session

RFC 6902 over SessionState. Paths are keyed, never array indexes (spec section 6.9). applyPatch writes these:

Declaration ​

ts
export type JsonPatchOp = {
  op: 'add' | 'replace' | 'test';
  path: string;
  value: JsonValue;
} | {
  op: 'remove';
  path: string;
} | {
  op: 'move' | 'copy';
  from: string;
  path: string;
};

Generic-API test (spec 3.1) ​

Rule Result
1. Neutral name pass: JsonPatchOp 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)