Swagger is configured and the API is richly decorated, but the spec only exists at runtime behind the running server. There is no committed or published openapi.json.
This has a concrete cost visible in this repo: the frontend and backend disagreed about the /api/v1 prefix (see the docker-compose issue), and /certificates/search rejects the obvious parameter name with no documented contract. A generated spec makes both mechanically checkable.
Suggested: add a script that boots the Nest app in-process, writes openapi.json via SwaggerModule.createDocument, and uploads it as a CI artifact. A follow-up could diff it per PR to surface unintended breaking changes.
Swagger is configured and the API is richly decorated, but the spec only exists at runtime behind the running server. There is no committed or published
openapi.json.This has a concrete cost visible in this repo: the frontend and backend disagreed about the
/api/v1prefix (see the docker-compose issue), and/certificates/searchrejects the obvious parameter name with no documented contract. A generated spec makes both mechanically checkable.Suggested: add a script that boots the Nest app in-process, writes
openapi.jsonviaSwaggerModule.createDocument, and uploads it as a CI artifact. A follow-up could diff it per PR to surface unintended breaking changes.