Is your feature request related to a problem? Please describe.
I need to use an ObjectMapperProcessor to customise JSON mappings (to support Scala's Option type, among other things), but the schemas generated by io.openapitools.swagger:swagger-maven-plugin don't reflect the mappings configured by the ObjectMapperProcessor because there is no way to tell the plugin about my ObjectMapperProcessor.
Describe the solution you'd like
Please add an option to specify the classname of the ObjectMapperProcessor implementation, which would affect the schema generation so that it matches the runtime behaviour when the ObjectMapperProcessor is installed.
Describe alternatives you've considered
I tried switching to io.swagger.core.v3:swagger-maven-plugin because it has a configuration option objectMapperProcessorClass, but it doesn't seem to work as expected: https://github.com/swagger-api/swagger-core/issues/3247
Is your feature request related to a problem? Please describe. I need to use an
ObjectMapperProcessor
to customise JSON mappings (to support Scala'sOption
type, among other things), but the schemas generated byio.openapitools.swagger:swagger-maven-plugin
don't reflect the mappings configured by theObjectMapperProcessor
because there is no way to tell the plugin about myObjectMapperProcessor
.Describe the solution you'd like Please add an option to specify the classname of the
ObjectMapperProcessor
implementation, which would affect the schema generation so that it matches the runtime behaviour when theObjectMapperProcessor
is installed.Describe alternatives you've considered I tried switching to
io.swagger.core.v3:swagger-maven-plugin
because it has a configuration optionobjectMapperProcessorClass
, but it doesn't seem to work as expected: https://github.com/swagger-api/swagger-core/issues/3247Additional context Swagger's
objectMapperProcessorClass
configuration option is documented here: https://github.com/swagger-api/swagger-core/wiki/Swagger-2.X---Integration-and-Configuration#configuration-properties