Releases: swagger-api/swagger-js
Releases · swagger-api/swagger-js
Swagger-Client 3.4.5 Released!
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 toa=[1,2,3]
, and is now serialized toa=1,2,3
.
- As an example: a request body of
Swagger-Client 3.4.4 Released!
Swagger-Client 3.4.3 Released!
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!
Swagger-Client 3.4.1 Released!
Swagger-Client 3.4.0 Released!
Interface changes: none.
Swagger-Client 3.3.5 Released!
Interface changes: none.
- Bugfix: object values in
application/x-www-form-urlencoded
request bodies are now stringified and escaped correctly
Swagger-Client 3.3.4 Released!
Interface changes: none.
- Improvement: modified
JSON.parse
/JsYaml.safeLoad
switching logic, it's now easier to slim down Swagger-Client if you don't need YAML parsing (via #1183)
Swagger-Client 3.3.3 Released!
Interface changes: none.
- Improvement: rewired JSON/YAML parsing logic, to allow for skinnier implementations for users that only need JSON (via #1175)
- Bugfix: covered RFC3986 requirements correctly in query parameter
allowReserved
processing (via #3817)
Swagger-Client 3.3.2 Released!
Interface changes: none.
- Improvement: relaxed Lodash version constraints to aid dependency flattening for users (via #1169)
- Bugfix: added support for React Native by switching from
isomorphic-fetch
tocross-fetch
(via #1158) - Bugfix: added safe access for operationId that threw errors for empty operations - which can be encountered while editing a definition (via #1157)
- Housekeeping: improved CI process to speed up builds (via #1170)
- Housekeeping: added a
build-dev
script that creates non-minified dist files (via #1172)