Releases: swagger-api/swagger-js
Swagger 2.1.5-M1 released!
A patch release for swagger-client has been released to address corner cases and add new functionality
New features:
- Support for the tag object from the 2.0 swagger spec, including description and external docs #243
- Options passed to underlying HTTP library by caller #229
Issues fixed:
Swagger-js v2.1.1-M1 Released!
The Swagger team is proud to announce the M1 release of three of our main libraries and tools: swagger-js, swagger-ui and swagger-core. All release provide official initial support for Swagger 2.0’s main features. The missing features will be added in the next milestone releases until the final release is available.
In order to better improve these libraries and tools, we ask that you start using them and provide us with feedback in form of issues on the github repository. The issues are a huge help in finding what’s missing or not working properly (though note some issues are already submitted). We would also appreciate any PRs that improve existing or new tickets.
These releases could not have happened without the intensive support of the Swagger community. Each of the projects had a few PRs that really helped us push these projects forward!
Be aware that the release notes contain the notable changes, but there may some changes that we missed in the list.
Notable Features:
- Available on npmjs.org
- First official milestone release of Swagger 2.0 support. Backwards compatible with Swagger 1.2.
- Unified API to initialize either 1.1, 1.2, 2.0 clients.
- Replace cake with gulp as the build tool.
- Rebuild the test framework with mocha and pure javascript.
- Addressed syntax issues which were breaking older versions of Internet Explorer
- Allow for repeated models of the same type in sample objects.
- Provide a example value for ‘date’ format.
- Please note that 2.1.1-M1 lives in Master
Notable Bug Fixes:
- Fixed query parameter encoding (#210)
- Fixed usage of content-type (#192)
- Fixed support for multi params with brackets (#191)
- Add array schema support (#147)
- Fix consumes/produces property propagation (#138)
- Added asCurl, mock modes for testing and debugging
Breaking Changes:
- The 1.x class, SwaggerApi, has been replaced with a unified SwaggerClient class.
Limitations: - There are 2.0 features which are NOT implemented, as described in the [milestones](https://github.com/swagger-api/swagger-js/milestones page)
v2.0.48
Swagger 2.0.48 has been released!
New features
- Refactored test framework. Now using mocha (#193)
- Added better support for sample JSON macros. You can provide interceptors to dynamically populate both model properties as well as operation parameters (#177)
- Added support for asCurl documentation, to show what a curl command would be based on any swagger operation. Includes headers, params, etc (#174)
- Default success and error callbacks implemented (#130)
- Configurable accept header when fetching swagger specifications (#120)
- Removed
global
scope for authorizations, allowing swagger-client to support multiple APIs in a single deployment (#109) - Added pass-through of
opts
when making requests
Defects fixed:
Please see https://groups.google.com/forum/#!forum/swagger-swaggersocket for the swagger google group, or http://webchat.freenode.net/?channels=swagger for IRC