Fixed and enhanced OpenAPI #195
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
adriendupuis
force-pushed
the
enh-openapi
branch
from
83dacb3 to
c23b5cf
Compare
adamwojs
approved these changes
Oct 5, 2025
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related PRs:
Description:
https://spec.openapis.org/oas/v3.1.1.html#x4-8-12-2-1-common-fixed-fields
https://swagger.io/docs/specification/v3_0/describing-parameters/#header-parameters
When using "Try it out' on live doc (
/api/ibexa/v2/doc#/Objects/api_contentobjects_contentId_get), the previously displayed Accept header parameter form input was never taken into account. To choose an Accept header, one must be selected in the Responses panel.So, I removed the useless and ignored Accept header parameter definition, and moved it's description up into the ressource description.
For QA:
Documentation: