Many of the classes provide overloaded static methods that makes it hard to make modifications without studying each client.
We should have a single unified public "builder" style API that users access to generate OpenAPI models and de-/serialize them to/from YAML or JSON. It is a goal to limit exposing internal smallrye-open-api types in this new API.
Currently, platforms integrating with smallrye-open-api make use of some combination of at least the following classes:
io.smallrye.openapi.api.OpenApiConfigio.smallrye.openapi.api.OpenApiDocumentio.smallrye.openapi.runtime.OpenApiProcessorio.smallrye.openapi.runtime.OpenApiStaticFileio.smallrye.openapi.runtime.io.OpenApiParserio.smallrye.openapi.runtime.io.OpenApiSerializerio.smallrye.openapi.runtime.scanner.AnnotationScannerExtensionio.smallrye.openapi.runtime.scanner.spi.AnnotationScannerMany of the classes provide overloaded static methods that makes it hard to make modifications without studying each client.
We should have a single unified public "builder" style API that users access to generate OpenAPI models and de-/serialize them to/from YAML or JSON. It is a goal to limit exposing internal smallrye-open-api types in this new API.