You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're using the JSpecify annotations (which will become the default nullability annotations in Spring Framework 7) and we encountered an issue with Swagger-core capabilities.
These nullability annotations are properly targeting TYPE_USE element type, which is currently not read at all by the io.swagger.v3.core.jackson.ModelResolver#resolve, making it impossible to set OpenAPI properties (such as eg. nullability) automatically.
Do you see any blocker why TYPE_USE annotations should not be considered by the ModelResolver?
Do you see any way around until the swagger-core is improved?
The text was updated successfully, but these errors were encountered:
We've encountered the same issue, I would expect to find the TYPE_USE annotations within io.swagger.v3.core.converter.AnnotatedType so they can be used when implementing a custom ModelConverter.
This issue is preventing us from deriving OpenAPI nullability from JSpecify annotations.
We're using the JSpecify annotations (which will become the default nullability annotations in Spring Framework 7) and we encountered an issue with Swagger-core capabilities.
These nullability annotations are properly targeting TYPE_USE element type, which is currently not read at all by the
io.swagger.v3.core.jackson.ModelResolver#resolve
, making it impossible to set OpenAPI properties (such as eg. nullability) automatically.The text was updated successfully, but these errors were encountered: