Skip to content

docs(openapi): declare GET /v1/customer/bycompany/{id} 200 envelope (#340)#341

Merged
CryptoJones merged 1 commit into
masterfrom
docs/openapi-customer-bycompany-response-shape
May 19, 2026
Merged

docs(openapi): declare GET /v1/customer/bycompany/{id} 200 envelope (#340)#341
CryptoJones merged 1 commit into
masterfrom
docs/openapi-customer-bycompany-response-shape

Conversation

@CryptoJones
Copy link
Copy Markdown
Owner

Closes #340.

Summary

Same missing-content-schema fix pattern as #312, #316, #326, #332 — now for the paginated list endpoint. Declare {message, count, limit, offset, customers: Customer[]} and pin with a test.

Test plan

  • npm run lint && npm test — 788 passing (was 787).

Proudly Made in Nebraska. Go Big Red! 🌽 https://xkcd.com/2347/

Same missing-content-schema pattern fixed for /v1/customer/{id}
in #312, POST /v1/customer in #316, POST /v1/timeentry in #326,
and POST /v1/customer/bulk in #332 — now for the paginated list
endpoint. The spec previously said only `description: 'OK'`, so
SDK generators reading the spec couldn't model the
Link-header-paired pagination envelope the controller emits:

    { message, count, limit, offset, customers: Customer[] }

Declare the shape and pin it with a test in
`tests/api/openapi.test.js`.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@CryptoJones CryptoJones merged commit f84fd45 into master May 19, 2026
3 checks passed
@CryptoJones CryptoJones deleted the docs/openapi-customer-bycompany-response-shape branch May 19, 2026 18:54
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.

OpenAPI: GET /v1/customer/bycompany/{id} 200 has no content schema

1 participant