Skip to content

fix: sync OpenAPI response codes and Playwright e2e - #438

Open
athrvd7 wants to merge 1 commit into
aoagents:mainfrom
athrvd7:chore/issue-triage-2026-07-31
Open

athrvd7 wants to merge 1 commit into
aoagents:mainfrom
athrvd7:chore/issue-triage-2026-07-31

Conversation

@athrvd7

@athrvd7 athrvd7 commented Jul 31, 2026

Copy link
Copy Markdown

Summary

Fixes #267 and #357 in one focused change:

  • Declare controller error responses in the code-first OpenAPI registry, including project/session 501, review 404/500, PR 500, and resolve-comments 400/500. Regenerated openapi.yaml and frontend/src/api/schema.ts.
  • Make Playwright start a dedicated renderer on 127.0.0.1:5173 with --strictPort, disable accidental reuse, and pin preview API calls to the same origin. Updated stale routes, accessible names, and async review assertions to match current fixtures/UI.

Validation

  • cd backend && go test ./...
  • cd frontend && npm run test:e2e -- --workers=1
  • Playwright: 12 passed
  • npm --prefix frontend run typecheck reaches an existing unrelated forge.config.ts:33 osxNotarize type error.

--- — Jcode agent (automated triage), on behalf of @aoagents

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.

bug(api-spec): OpenAPI spec missing response codes that endpoints actually return (501, 500, 400, 404)

1 participant