Releases: swagger-api/swagger-js
Releases · swagger-api/swagger-js
Swagger-Client 3.8.5 Released!
Swagger-Client 3.8.4 Released!
Swagger-Client 3.8.3 Released!
Swagger-Client 3.8.1 Released!
Interface changes: none.
Changelog:
- bugfix: $ref + allOf interation in the resolver (via #1275, #1309)
- bugfix: deep $ref resolution issue based on data order in a document (via #1243)
- bugfix: relative URL construction based on remote definition URL (via #1312)
- dependency: upgrade to
deep-extend@^0.5.1to avoid potential prototype pollution security issue (via #1304) - meta: multiple issue templates, to encourage higher-quality reports (via #1311)
Swagger-Client 3.8.0 Released!
This release introduces a new attachContentTypeForEmptyPayload option that attaches Content-Type headers when an operation calls for a body but no value is provided.
There are also some minor changes to requestContentType: it now allows control over Content-Type when no body value is provided.
Swagger-Client 3.7.2 Released!
Fixes a regression related to parameter normalization that was causing an infinite loop; see swagger-api/swagger-ui#4466 and swagger-api/swagger-ui#4467.
Swagger-Client 3.7.1 Released!
Interface changes: none.
Changelog:
- bugfix: groups of multiple referenced inherited parameters are now handled correctly by
resolveSubtree(via #1295)
Swagger-Client v3.7.0 Released!
Interface changes: v2OperationIdCompatibilityMode option is now available. You can use it to generate v2-style names for operations in the tags interface.
Changelog:
Swagger-Client 3.6.0 Released!
Swagger-Client 3.5.2 Released!
Interface changes: none.
Changelog:
- bugfix: whole-document remote references (e.g.
$ref: "./myOtherDoc.json") are no longer erroneously flagged as indirect circular references (via #1265)