Skip to content

Define error 701 for a request body without a required member - #247

Merged
lorandmolnar merged 2 commits into
developfrom
fix/238-missing-member-701
Nov 9, 2026
Merged

lorandmolnar merged 2 commits into
developfrom
fix/238-missing-member-701

Conversation

@lorandmolnar

@lorandmolnar lorandmolnar commented Nov 9, 2026 •

Copy link
Copy Markdown
Collaborator

Closes #238. Working group decision of 2026-11-09: 701 accepted.

Changes:

  • schemas.yaml, errorObject_701: the description names both triggers, a request body that lacks a member the request schema marks as required, and the empty object where minProperties applies (Empty object body on value-write endpoints: 701 or successful no-op? #226).
  • JSON_for_IO-Link_unmerged.yaml: POST /masters/{masterNumber}/ports/{portNumber}/power declares 701 under HTTP 400, since its request schema (PortPowerMode, required primaryPower) was the only JSON body with a required member whose operation declared no 701. Every other operation with required request members already declares 701. POST /devices/{deviceAlias}/fwupdate (multipart/form-data) is left unchanged.

Spectral lint and swagger-merger pass.

Working group decision of 2026-11-09 on issue #238.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@lorandmolnar
lorandmolnar merged commit 62b86c7 into develop Nov 9, 2026
6 checks passed
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.

Request body without a mandatory member: 201, 202 or 701?

2 participants