Releases: swagger-api/swagger-js
Releases · swagger-api/swagger-js
Swagger-JS 3.0.18 Released!
Swagger-JS 3.0.16 Released!
Swagger-JS 3.0.15 Released!
Interface changes: None.
- README updates and improvements
- Configured the default resolver fetch implementation to send cookies and Authorization headers for same-origin requests (see #1083)
- Developer note: removed
package-lock.json
from the repository, as it was causing problems.
Swagger-JS 3.0.14 Released!
Interface changes: None.
- Fixed a defect in
__originalOperationId
logic (swagger-api/swagger-ui#3203) and added more tests around the functionality - Added throw when execute can't find a requested operation
Swagger-JS 3.0.12 Released!
Interface changes: New resolve options, see below.
- Improvement:
parameterMacro
andmodelPropertyMacro
options inresolve
(via #1067)
Swagger-JS 3.0.10 Released!
Interface changes: Client interface method names may differ if you have duplicate operationIds in your spec. Note that this is not a breaking change, as duplicate operationIds were previously undefined behavior.
Swagger-JS 3.0.9 Released!
Interface changes: no longer need to manually stringify request bodies for execute.
Swagger-JS 3.0.8 Released!
Swagger-JS 3.0.3 Released!
Interface changes: No runtime interface changes, but the bundle file is now exported as a UMD module.
- Added
loadSpec
option tofetch
that allows optimistic loading of a resource as text, regardless of responseContent-Type
- Added authorizations to instance
execute
- Fixed an issue where path and operation parameters weren't being merged (#965)
- Added
contextUrl
option that allows user to specify the URL that a spec is in the context of
Swagger-JS 3.0.2 Released!
Interface changes: None
- the
Access-Control-Allow-Origin: *
header is no longer attached to all requests