Skip to content

ModelConverterRegistrar should care the order #2704

Closed
@abccbaandy

Description

@abccbaandy

Is your feature request related to a problem? Please describe.

I got the oneOf property is not work issue, but no fix yet.
swagger-api/swagger-core#4732

In the meantime, I am working on my own ModelConverter to hack the result.
I use this code to add my converter.

        ModelConverters.getInstance().addConverter(new MyCustomResolver());

But I found the Springdoc have its own converter too, and it overwrite my result.
I think the reason is because the order of the converters in ModelConverters.

Describe the solution you'd like
Maybe just use Spring @Order annotation?

Metadata

Metadata

Assignees

No one assigned

    Labels

    invalidThis doesn't seem right

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions