⚠️ OpenSpec-managed issue — this content is automatically synced
from the openspec/ directory. Manual edits will be overwritten on next sync.
Artifacts
Summary
A developer at a municipality or a supplier reads the catalogue API from generated documentation instead of hand-written pages: the catalogue objects as OpenRegister describes them, and stackiq's own endpoints as the code describes them. Both open from one API documentation page in stackiq, and both download as OpenAPI files. The generated file in the repository stops being empty.
Specs
Tasks
Design
See design.md for technical design details.
Synced from openspec/changes/sharing-generated-api-docs by OpenSpec workflow
App: stackiq
Artifacts
Summary
A developer at a municipality or a supplier reads the catalogue API from generated documentation instead of hand-written pages: the catalogue objects as OpenRegister describes them, and stackiq's own endpoints as the code describes them. Both open from one API documentation page in stackiq, and both download as OpenAPI files. The generated file in the repository stops being empty.
Specs
Tasks
composer openapi:checkexit 0; PHPUnit unchanged)composer check:strictincluding openapi:check)tests/vitest/openApiReader.spec.js; Playwrighttests/e2e/workflows/api-docs.spec.ts)tests/Unit/Controller/AangebodenGebruikControllerTest.phpdocs case; docs build with a screenshot)Design
See design.md for technical design details.
Synced from
openspec/changes/sharing-generated-api-docsby OpenSpec workflowApp:
stackiq