Releases: openapi-processor/openapi-processor-spring
2023.1.1
2023.1
this release includes a couple of mapping improvements for bean validations & annotation mapping. Both will work on mapped types. It also brings bean validation v3 support for Spring Boot 3.
See the core release notes 2023.1 for a detailed description of the changes.
dependency updates
- updated openapi-processor-core to 2023.1 (was 2022.6)
2022.5
openapi-processor has a new annotation type mapping feature to add additional annotations to model classes or endpoint parameters. It also adds a @Generated
annotation that replaces the generated text header in the generated files.
See the core release notes 2022.6 for a detailed description of the changes.
#131, @HeadMapping/@TraceMapping/@OptionsMapping do not exist
by @mikrethor
a few http methods do not have an explicit mapping annotation: @HeadMapping
, @TraceMapping
, @OptionsMapping
.
The processor now generates @RequestMapping(method = RequestMethod.
{http method} ))
.
dependency updates
- updated openapi-processor-core to 2022.6 (was 2022.5)
2022.4
openapi-processor offers a new OpenAPI 3.0 & 3.1 parser and fixes missing bean validation imports
- OpenAPI 3.0 support includes JSON schema validation with detailed reporting.
- OpenAPI 3.1 support is experimental and does not yet support schema validation.
See the core release notes 2022.5 for a detailed description of the changes.
dependency updates
- updated openapi-processor-core to 2022.5 (was 2022.4)
2022.3
2022.2
an update with a few bug fixes.
See the core release notes for a detailed description of the changes.
dependency updates
- updated openapi-processor-core to 2022.2 (was 2021.1)
2022.1
an update with two small improvements.
See the core release notes for a detailed description of the changes.
dependency updates
- updated openapi-processor-core to 2022.1 (was 2021.6)
2021.6
#133, improved error reporting
Sometimes parsing errors of the OpenAPI description were not be properly reported (e.g. by the maven plugin). Parsing/validation errors are now handled and reported at the processor level and reporting no longer depends on the plugin that calls the processor (gradle/maven).
#134, nested oneOf & anyOf
if an oneOf
/anyOf
was used in a schema property the processor generated code that used a non-existing class as java type for the property.
dependency updates
- updated openapi-processor-core to 2021.6 (was 2021.5)
- updated swagger parser to 2.0.28 (was 2.0.27)
2021.5
openapi-processor/openapi-processor-core#68, improved response type handling
This is a breaking change because it changes the code that gets generated by default. To keep the old behavior set result-style
in the mapping.yaml to all
:
openapi-processor-mapping: v2
options:
package-name: ...
map:
result-style: all
See the core release notes for a detailed description of the change.
dependency updates
- updated openapi-processor-core to 2021.5, (was 2021.4)
- updated swagger parser to 2.0.27 (was 2.0.26)
2021.4
This release has several bug fixes and a couple of improvements for multipart requests and bean-validation. A new feature is the ability to automatically add a model-name-suffix
to all generated model classes.
See the core release notes for all the details.
- updated openapi-processor-core to 2021.4, (was 2021.3.1)
- updated swagger parser to 2.0.26 (was 2.0.25)