This repository was archived by the owner on Mar 16, 2025. It is now read-only.
2022.5
#96
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
OpenAPI 3.0 parser & JSON schema validation
openapi-processor provides another OpenAPI 3.0 parser. It includes JSON schema validation with detailed reporting.
To enable it, set the parser configuration to
INTERNAL.OpenAPI 3.1 (experimental)
The internal OpenAPI parser does support OpenAPI 3.1 but does not yet support schema validation.
To enable it, set the parser configuration to
INTERNAL. It will automatically detect OpenAPI 3.0 & 3.1.The processor does handle the renamed/changed OpenAPI 3.1 properties as needed for code generation:
typekeywordThe
typekeyword allows a list of types. Defining anullabletype is done by adding"null"to the list of types.The processor does support the new
nullabledefinition. Apart from that it will use the first non-null type as the type for code generation.exclusiveMinimumandexclusiveMaximumkeywordswhich is used for adding bean validations.
openapi-processor/openapi-processor-spring#141, missing import for javax.validation.constraints.Pattern
the
imports for bean validation annotations were missing for item constraints of a mapped array. Having an api description like thisand a mapping
did not generate the
javax.validation.constraints.Patternimport.(ignore the
@Mapping/@Parameterannotations, this is pseudo code used by the integration tests)This discussion was created from the release 2022.5.
Beta Was this translation helpful? Give feedback.
All reactions