Skip to content

Declare error 103 under HTTP 404 on every operation - #248

Merged
lorandmolnar merged 2 commits into
developfrom
fix/239-error-103-status
Nov 9, 2026
Merged

lorandmolnar merged 2 commits into
developfrom
fix/239-error-103-status

Conversation

@lorandmolnar

@lorandmolnar lorandmolnar commented Nov 9, 2026 •

Copy link
Copy Markdown
Collaborator

Closes #239. Working group decision of 2026-11-09: 404 accepted.

Changes:

  • Introduction, error behavior rule (e): states HTTP status 404 (Not Found) for error 103, so the rule is machine-readable in every operation.
  • schemas.yaml, errorObject_103: the description states the 404 status.
  • POST /masters/{masterNumber}/ports/{portNumber}/power: 103 moved from the 400 to the 404 response.
  • POST /devices/{deviceAlias}/parameters/{parameterIdent}/value and POST .../subindices/{subParameterIdent}/value: the duplicate 103 under 400 removed; the 404 response keeps it.

After this change all 24 declarations of 103 are under 404. Spectral lint and swagger-merger pass.

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

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@roesekoSICKAG
roesekoSICKAG self-requested a review November 9, 2026 14:42
@lorandmolnar
lorandmolnar merged commit a539849 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.

Error 103 (Operation not supported) is declared under HTTP 404 on 21 operations and under 400 on three

2 participants