Releases: swagger-api/swagger-js
Releases · swagger-api/swagger-js
Swagger-Client 3.5.1 Released!
04 Mar 03:39
Compare
Sorry, something went wrong.
No results found
Interface changes : none.
Changelog :
improvement: specmap mergeDeep JSON patches now intelligently take shortcuts if source and destination object properties do not conflict (via #1217 )
dependency: moved to fast-json-patch@2, which solves an issue that was blocking React Native users from using the library (via #1253 )
Swagger-Client v3.5.0 Released!
24 Feb 09:08
Compare
Sorry, something went wrong.
No results found
Interface changes : Added Swagger.resolveSubtree.
Changelog :
Added a subtree-discriminating resolver interface to Specmap, for more performant resolution in downstream projects (via #1248 )
Swagger-Client v3.4.11 Released!
10 Feb 04:49
Compare
Sorry, something went wrong.
No results found
FYI: 3.4.10 was mistakenly built from an older commit during 3.4.9's deploy process, so 3.4.11 was released to supersede them both.
Interface changes : none.
Changelog :
bugfix: ignore more freely-named key positions; reducing erroneous $ref and allOf parsing (via #1195 )
housekeeping: add more tests to check freely-named key position avoidance (via #1240 )
Swagger-Client 3.4.8 Released!
03 Feb 08:34
Compare
Sorry, something went wrong.
No results found
Interface changes : none.
Improvement(specmap): $$ref meta patches are no longer erronously attached to $ref targets (via #1237 )
Bugfix(oas3-execute): style: deepObject is now built correctly (via #1235 )
Bugfix: http.withCredentials flag is now correctly applied (via #1236 )
Swagger-Client 3.4.7 Released!
27 Jan 05:03
Compare
Sorry, something went wrong.
No results found
Interface changes : none.
Improvement: target JSON, XML, YAML, and text media types more precisely in shouldDownloadAsText logic (via #1227 )
Bugfix: HTTP agent withCredentials flag now works as expected (via #1189 )
Swagger-Client v3.4.6 Released!
20 Jan 21:39
Compare
Sorry, something went wrong.
No results found
Interface changes : none.
Improvement: application/yaml is now advertised as an acceptable media type when fetching remote decoments (via #1232 )
Bugfix: __originalOperationId is now more performant and accurate (via #1225 )
Swagger-Client 3.4.5 Released!
16 Jan 01:21
Compare
Sorry, something went wrong.
No results found
Interface changes : none.
Bugfix: OAS3 Array request body key values are now comma-seperated instead of being JSON-stringified (via #1233 )
As an example: a request body of { a: [1, 2, 3] } was originally serialized to a=[1,2,3], and is now serialized to a=1,2,3.
Swagger-Client 3.4.4 Released!
30 Dec 06:59
Compare
Sorry, something went wrong.
No results found
Interface changes : none.
Improvement: $ref resolver now ignores $ref keys in freely-named key positions within the Swagger/OpenAPI specification (via #1214 )
Housekeeping: test suite npm scripts now run correctly in Windows (via #1208 )
Swagger-Client 3.4.3 Released!
23 Dec 06:59
Compare
Sorry, something went wrong.
No results found
Interface changes : none.
Performance: $ref resolver lookaside was reimplemented, which should significantly improve the performance of larger API definitions (via #1209 )
Swagger-Client 3.4.2 Released!
16 Dec 07:56
Compare
Sorry, something went wrong.
No results found
Interface changes : none.
Bugfix: non-ASCII characters are now percent-encoded correctly (via #1204 )
Bugfix: Unicode surrogate pairs are now percent-encoded correctly (via #1205 )
Bugfix: normalization no longer results in incorrect parameter ambiguity warnings (via #1180 )
Version diff