-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Catalogi API: API documentation incorrect #1976
Comments
PR's are welcome anytime :-) |
…on for publish actions The publish actions were missing the correct summary, description and possible response status codes documentation.
…on for publish actions The publish actions were missing the correct summary, description and possible response status codes documentation.
@michielverhoef I've created a PR: VNG-Realisatie/catalogi-api#130 I'd like to argue to get this in Catalogi API 1.1.1 rather than 1.2.0, since there is effectively a bug in the documentation - the publish endpoint documents a response status code HTTP 201, but in reality this is a HTTP 200 |
…on for publish actions The publish actions were missing the correct summary, description and possible response status codes documentation.
…on for publish actions The publish actions were missing the correct summary, description and possible response status codes documentation.
…on for publish actions The publish actions were missing the correct summary, description and possible response status codes documentation.
…on for publish actions The publish actions were missing the correct summary, description and possible response status codes documentation.
As this has been fixed the issue will be closed. |
Bug
In the Catalogi API, the "publish" actions are not correctly documented, e.g. https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/VNG-Realisatie/catalogi-api/1.1.0/src/openapi.yaml#operation/besluittype_publish
The response status code is HTTP 200 instead of the documented HTTP 201, and the titles/summaries of the operations in the API spec also do not correctly reflect the behaviour.
This has been fixed in Open Zaak, so we can probably contribute that back relatively easily.
Additionally, the error response status codes are missing for these actions (HTTP 4xx, HTTP 5xx)
The text was updated successfully, but these errors were encountered: