Describe the bug
After upgrading from springdoc 2.1.0 to springdoc 2.2.0, a new behavior is occurring that is breaking our openapi doc generated.
If you are using Jakarta Collections validator on controller query parameters (for example @Size in my case) the minItems and maxItems are added to the openapi doc generated as expected but it is also adding now the maximum/minimum (with the same number as minItems and maxItems) to the type of the items contained in the collection.
To Reproduce
Steps to reproduce the behavior:
Use @Size on Set for example for a query parameter in your controller methods
What version of spring-boot you are using?
spring-boot 3.1.2
What modules and versions of springdoc-openapi are you using?
springdoc-openapi-starter-common-2.2.0.jar
springdoc-openapi-starter-webflux-api-2.2.0.jar
What is the actual and the expected result using OpenAPI Description (yml or json)?
actual:
Describe the bug After upgrading from springdoc 2.1.0 to springdoc 2.2.0, a new behavior is occurring that is breaking our openapi doc generated. If you are using Jakarta Collections validator on controller query parameters (for example @Size in my case) the minItems and maxItems are added to the openapi doc generated as expected but it is also adding now the maximum/minimum (with the same number as minItems and maxItems) to the type of the items contained in the collection.
To Reproduce Steps to reproduce the behavior: Use @Size on Set for example for a query parameter in your controller methods
expected:
Expected behavior @Size should only affect the number of items in the collection not the size of the type contained in the collection
Screenshots
Additional context We are using Kotlin