upgrade swagger-core from 2.2.53 to 2.2.54 - #3351
Conversation
04c6b5e to
02905ac
Compare
70999df to
33e56fd
Compare
33e56fd to
90bc94a
Compare
90bc94a to
d78abd9
Compare
swagger-core now resolves java.time.Duration, LocalTime and OffsetTime itself (swagger-api/swagger-core#5184), so the corresponding entries of initExtraSchemas can be dropped.
|
Merged, thanks @Mattias-Sehlstedt. Full suite is green on both lines. Backported to Recorded in the changelog under Changed, flagging the visible consequence for users: |
|
Hi, With SpringDoc 3.1.0 generating OAS in version 3.0, it gives this OAS: "localTime": {
"type": "string"
},With SpringDoc 3.1.1 generating OAS in version 3.0, it gives this OAS: "localTime": {
"properties": {
"hour": {
"format": "int32",
"type": "integer"
},
"minute": {
"format": "int32",
"type": "integer"
},
"nano": {
"format": "int32",
"type": "integer"
},
"second": {
"format": "int32",
"type": "integer"
}
},
"type": "object"
}I think we should keep the extra schemas when Best regards, |
Swagger-core has implemented better handling for dates in swagger-api/swagger-core#5184. This means that some parts of
ExtraSchemasfrom ec43ffb can be removed, since they are now handled upstream.