📝 docs: second error format — 412 + bare Spring validation array #123
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/412-error-format"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Document the API's second error format in the field notes (roadmap §2.3, issue #68):
Client-side handling of the array shape (
_response_detail/_api_error) stays out of scope — tracked in #101.Closes #68.
Evidence
devices.md; the conventions section lists no412and no second shape.After:
README.md(docs) documents the format with the observed example, the three endpoints (users/{id}/refreshtoken,gateways/{id}/network,companies/installation-company-by-installer-email), thecode/codesfield, the list-not-dict hazard, and adds412to typical codes;devices.mdlinks to it.Docs-only change, no code touched. Test suite: 139 passed (unchanged baseline).
Merge Danger
Door: two-way (docs-only, trivially revertible)
Blast Radius: none — documentation only.
WIP: 📝 docs: second error format — 412 + bare Spring validation arrayto 📝 docs: second error format — 412 + bare Spring validation array