expose option for openapi version#216
Merged
EnriqueL8 merged 1 commit intohyperledger:mainfrom Apr 28, 2026
Merged
Conversation
Signed-off-by: John Hosie <john.hosie@kaleido.io>
EnriqueL8
approved these changes
Apr 28, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
When using certain JSON schema constructs ( such as specifying type as an array), the generated API document will fail validation because those syntax were introduces in JSON Schema draft 2019-09. OpenAPI 3.0.x aligns with earlier JSON Schema drafts where type MUST be a single string.
Open API 3.1.1 aligned with JSON Schema 2020-12 where type may be a string or an array of unique strings .
So rather than hard coding the openapi version, this PR allows it to be configurable, but continues to default to
3.0.2