Releases: papsign/Ktor-OpenAPI-Generator
Releases · papsign/Ktor-OpenAPI-Generator
Added Byte And Short type to primitive parsers
- Added
Byte
AndShort
types to primitive parsers
Fixed previous release
Fixed previous release sending wrongful errors on nullable types.
Replaced validation NPE with OpenAPIRequiredFieldException
- Replaced validation NPE with
OpenAPIRequiredFieldException
Changed KClass and Reified to KType
- Added documentation on common methods
- Changed KClass to Ktype in Most parts of the project
- Changed Behavior of Module Provider to reflect the changes
- /!\ Dependencies of dependent modules are registered before the module, unless they are already present.
- Fixed sercurity scheme not being generated due to chnages
Changed logback to SLF4J
- Changed logback to SLF4J to prevent "Class path contains multiple SLF4J bindings"
Added status code modules, changed Module provider to be KType based instead of KClass based
- Added Status Modules and corresponding utility functions
- Changed Module provider to use KTypes instead of KClasses; Broken code needs to either specify
type = x::class.startprojectedType
or use the reified inline version ofregisterModule
depending on what the desired behavior is. - Changed Module provider to Guarantee insertion order while preserving HashSet Uniqueness for retro compatibility. Last insertions are guaranteed to be at the end of the
ofType
returned collection now, allowing to use the module provider like a stack.
Generic Body Types
- Generic body types can now be properly parsed
Any code implementing a custom parser module will break, but the changes in behaviour are very minor, jut get the classifier from the KType.
String Constraints
- Added various string constraint annotations
Added `@Description` and `@StringExample`
- Added
@Description
to describe the openapi models - Added
@StringExample
to conveniently add string examples to openapi models
Fixed Examples not generating the right OpenAPI definition
- Examples now follow the right spec-compliant model.