Skip to content

docs(api): TRA-740 BB42 F3 — uniform accept-if-matches on http-method-coverage#156

Merged
mikestankavich merged 1 commit into
mainfrom
worktree-tra-740-bb42-f3-http-method-coverage
May 16, 2026
Merged

docs(api): TRA-740 BB42 F3 — uniform accept-if-matches on http-method-coverage#156
mikestankavich merged 1 commit into
mainfrom
worktree-tra-740-bb42-f3-http-method-coverage

Conversation

@mikestankavich
Copy link
Copy Markdown
Contributor

Summary

  • Drops the artificial two-category split (round-trip-safe vs dedicated-mutation-surface) in the application/merge-patch+json paragraph on /docs/api/http-method-coverage.
  • Describes accept-if-matches uniformly: matching value → silently stripped (enabling verbatim GETPATCH round-trip); differing value → 400 read_only naming the dedicated write path.
  • Cross-page check: /docs/api/resource-identifiers and /docs/api/errors already describe the uniform rule correctly (BB39 work) — no edits needed there.

Why

BB42 verified that external_key, tags, and parent_external_key all return 200 on verbatim echo and only 400 on mismatch — same as id/timestamps/location_external_key. The previous prose promised an unconditional 400 for the second-category fields, which an integrator following the full-object round-trip pattern would never observe. Two failure modes (verbatim echo vs stale-cache rewrite) diverged silently in the contract.

No platform changes — service behavior is correct.

Test plan

  • pnpm typecheck
  • pnpm build
  • pnpm dlx prettier --check docs/api/http-method-coverage.md
  • Grep confirms no remaining "unconditional 400" / two-category wording on the page
  • Cross-page grep confirms resource-identifiers.md and errors.md describe accept-if-matches uniformly

Closes TRA-740.

🤖 Generated with Claude Code

…-coverage

Drop the artificial two-category split (round-trip-safe vs dedicated-
mutation-surface) on /docs/api/http-method-coverage. The service applies
accept-if-matches uniformly: a verbatim echo of any read-only field is
silently stripped, and a differing value returns 400 read_only with the
dedicated write path. Aligns the merge-patch semantics paragraph with
the per-field accounting already in resource-identifiers and errors
(BB39 work).

Verified live: external_key, tags, and parent_external_key all 200 on
verbatim echo and 400 only on mismatch — same as id/timestamps/
location_external_key. Cross-page check on resource-identifiers and
errors confirms both already describe the uniform rule correctly; no
edits needed there.
@github-actions
Copy link
Copy Markdown

🚀 Preview Deployment Update

✅ This PR has been successfully merged into the preview branch.

The preview environment will update shortly at: https://docs.preview.trakrf.id

@cloudflare-workers-and-pages
Copy link
Copy Markdown

cloudflare-workers-and-pages Bot commented May 16, 2026

Deploying docs with  Cloudflare Pages  Cloudflare Pages

Latest commit: bb488d4
Status: ✅  Deploy successful!
Preview URL: https://a09d2ad1.docs-4n7.pages.dev
Branch Preview URL: https://preview.docs-4n7.pages.dev

View logs

@mikestankavich mikestankavich merged commit f3c2109 into main May 16, 2026
2 checks passed
@mikestankavich mikestankavich deleted the worktree-tra-740-bb42-f3-http-method-coverage branch May 16, 2026 11:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant