fix(openapi-spec): honor declared success statuses in generated responses - #2900
Conversation
|
Warning Review limit reachedNext included review available in 17 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (13)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e9b9028f17
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
📊 Benchmark Results✅ All benchmarks passed
Updated: 2026-09-24T15:20:47.452Z · Commit: cc7fe33 |
Summary
successStatusdeclared on a route now reaches the extracted route contract, OpenAPI success response, JSON success response coverage, generated client, and HTTP transport. Routes without an explicit status retain their existing 200 response for JSON and 204 response for an empty result. A route with an output schema cannot declare bodyless 204 or 205.Closes #2316.
Validation
Elevated profile on head
cc7fe332cbf76fcca4ac8516b26a2cc490ae9620. Independent code review and verifier reviews passed with no actionable findings.pnpm strict-contract-typecheckpasses with 0 added and 0 removed diagnostics. The updated PR CI will validate the merge candidate.Visual evidence
The generated RouteIR documentation was checked at 1280×720 and 390×844, with no console errors or horizontal overflow.
Integration
cc7fe332cbf76fcca4ac8516b26a2cc490ae9620; current base:67a0380e0a52d44a20039d806920876c6f6ecadc.757f710452eff7a908d82e1244a231d137299a97. The latest base commit changes only webhook retry files and a changeset.36013252956failedstrict-contract-typecheck; generated-apps and split-validation-shadow failures followed from that gate. The new head fixes this cause.