fix(ext-openapi): one shared answer per status, not a numbered family #24

Merged

Relism merged 1 commits from fix/openapi/one-shared-answer-per-status into master

2026-09-23 16:34:15 +00:00

Author	SHA1	Message	Date
Zakaria El OrcheandClaude Opus 5	5fe6fb46c8	fix(ext-openapi): one shared answer per status, not a numbered family Hoisting named a shared response after its status and disambiguated with a counter, so a document with three wordings for 403 grew Forbidden, Forbidden2 and Forbidden3 in its components. Numbered names say nothing and move as soon as a route is added. The answer a status is usually given is now the one hoisted, under that status's own name, and a route that answers the same status differently keeps its wording inline where it belongs. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-23 16:34:13 +00:00

Author

SHA1

Message

Date

Zakaria El OrcheandClaude Opus 5

5fe6fb46c8

fix(ext-openapi): one shared answer per status, not a numbered family

Hoisting named a shared response after its status and disambiguated with a
counter, so a document with three wordings for 403 grew Forbidden, Forbidden2
and Forbidden3 in its components. Numbered names say nothing and move as soon
as a route is added.

The answer a status is usually given is now the one hoisted, under that
status's own name, and a route that answers the same status differently keeps
its wording inline where it belongs.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-09-23 16:34:13 +00:00