Skip to content

OpenAPI version 3.1 produces no custom schema and defaults to string schema when dependency springwolf-amqp is present #3079

@MoellJ

Description

@MoellJ

Describe the bug

When using springdoc with OpenAPI version 3.1 and springwolf-amqp, no custom schemas are generated and all schemas default to "schema": {"type": "string"}
Setting springdoc.api-docs.version=openapi_3_0 or downgrading springdoc to 2.7.x fixes this but is undesirable.
When removing the springwolf dependency, springdoc functions as expected even with OpenApi version 3.1

"responses": { "200": { "description": "Successful operation", "content": { "application/json": { "schema": { "type": "string" } } } }

To Reproduce
Steps to reproduce the behavior:

springdoc-openai version: 2.8.11 (Through springdoc-openapi-starter-webmvc-ui)
springwolf-amqp version: 1.16.0
spring-boot version: 3.5.5

  • TODO Provide with a sample code (HelloController) or Test that reproduces the problem

Expected behavior
Same schema that would be generated without springwolf present

Additional context
Seems a bit similar to #2972 but not quite the same

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions