fix(metadata-protocol,rest,objectql): a batch/import ROW reports a unique-constraint refusal as UNIQUE_VIOLATION, the route's one wire spelling
#20814
pr-automation.yml
on: pull_request
Check PR Size
Check Changeset
52s
Auto Label
Annotations
2 notices
|
Check Changeset:
.changeset/import-row-unique-violation-rest.md#L0
ADR-0087 exemption (no-migration-prescription): Nothing authorable moves: no spec key, export, config field or stored metadata changes spelling or shape, `packages/spec` is untouched and `objectstack migrate meta` has nothing to rewrite. What moves is the `code` value one import row report carries for one condition — the wire report of a driver's unique-constraint refusal on the per-row surface of `POST /api/v1/data/:object/import` — which now spells the standard-catalog member the whole-request door and the published protocol docs already use. The consumer note below is guidance for a client branching on that row code; it prescribes no rewrite of any authored artifact.
|
|
Check Changeset:
.changeset/batch-row-unique-violation-metadata-protocol.md#L0
ADR-0087 exemption (no-migration-prescription): Nothing authorable moves: no spec key, export, config field or stored metadata changes spelling or shape, `packages/spec` is untouched and `objectstack migrate meta` has nothing to rewrite. What moves is the `code` value one REST response row carries for one condition — the wire report of a driver's unique-constraint refusal on the per-row surface of `POST /api/v1/data/:object/batch` — which now spells the standard-catalog member the whole-request doors and the published protocol docs already use. The consumer note below is guidance for a client branching on that row code; it prescribes no rewrite of any authored artifact.
|