chore(deps): update dependency swagger-client to v3#25
Open
chore(deps): update dependency swagger-client to v3#25
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^2.1.28->^3.0.0Release Notes
swagger-api/swagger-js
v3.9.6Compare Source
Changelog
npm audit fix(#1484)v3.9.5Compare Source
Changelog
Accept: application/json, application/yamlfor all document fetches (#1478)npm auditconcerns (#1474)v3.9.4Compare Source
Changelog
Parameter.contentvalues (#1469)v3.9.3Compare Source
This release includes a fix that prevents resolution of
$refkeys in OpenAPI 3.0 Media Type Objects that are within a Request Body Object or Response Object.Changelog
v3.9.2Compare Source
This release includes housekeeping tasks that should resolve all current
npm auditadvisories displayed when installing Swagger Client.Changelog
@kyleshockey/js-yaml->js-yaml(via #1459)v3.9.1Compare Source
This release pins our
fast-json-patchdependency to~2.1.0in order to avoid a runtime error users were encountering in #1460.No source changes are included.
v3.9.0Compare Source
This release includes a new
useCircularStructuresoption that instructs Swagger Client to represent circular references with circular JavaScript objects, as well as fixes in Specmap for documents with nested allOf/$ref values.Changelog
traverseto production dependencies (via #1443)test:webpackfrom release configuration (via #1441)v3.8.26Compare Source
This release was unpublished on npm because it was missing a production dependency, which was fixed in #1443. Use
swagger-client@3.9.0instead.v3.8.25Compare Source
This patch release fixes a bug related to the usage of path parameter templating more than once within a Path Item Object's key.
Changelog
v3.8.24Compare Source
Summary
Small patch release that includes a fix for the resolver improperly processing
$refvalues inside of Schema Object'sitems.example.Changelog
example(via #1423)v3.8.23Compare Source
Changelog:
JSON.parsemethod for all types and encodings of JSON (via #1419)v3.8.22Compare Source
v3.8.21Compare Source
Interface changes: none.
Changelog:
0when percent-encoding characters (via #1386)v3.8.20Compare Source
Interface changes: none.
Changelog:
v3.8.19Compare Source
FYI: Swagger Client
3.8.16,3.8.17, and3.8.18can be ignored - they were created in the process of troubleshooting a release script.Interface changes: none.
Changelog:
isFilecompatible with React Native (via #1374)v3.8.18Compare Source
v3.8.17Compare Source
v3.8.16Compare Source
v3.8.15Compare Source
Interface changes: none.
Changelog:
v3.8.14Compare Source
v3.8.13Compare Source
Interface changes: none.
v3.8.12Compare Source
Interface changes: none.
Changelog:
nullparameter values (via #1363)v3.8.11Compare Source
Interface changes: none.
Changelog:
Reverts
v3.8.10Compare Source
Interface changes: none.
Changelog:
js-yamlfork (#1353)function.prototype.name(via #1351)v3.8.8Compare Source
This version serves as a stopgap for #1335 - it should resolve any issue around utilizing the resolver in a minified environment.
v3.8.7Compare Source
Interface changes: Parameters with
allowEmptyValue: trueare no longer (incorrectly) automatically included in requests - you must set the parameter value to an empty string, otherwise it will be omitted.Changelog:
babel-runtimedependency (via #1203)allowEmptyValueparameters (via #1333)export defaultsyntax for top-level module (via #1318)v3.8.6Compare Source
Fixes a dependency issue reported in #1326.
v3.8.5Compare Source
Interface changes: none.
Changelog:
v3.8.4Compare Source
Interface changes: none.
Changelog:
v3.8.3Compare Source
Interface changes: none.
Changelog:
v3.8.2Compare Source
v3.8.1Compare Source
Interface changes: none.
Changelog:
deep-extend@^0.5.1to avoid potential prototype pollution security issue (via #1304)v3.8.0Compare Source
This release introduces a new
attachContentTypeForEmptyPayloadoption that attachesContent-Typeheaders when an operation calls for a body but no value is provided.There are also some minor changes to
requestContentType: it now allows control overContent-Typewhen no body value is provided.v3.7.2Compare Source
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.
v3.7.1Compare Source
Interface changes: none.
Changelog:
resolveSubtree(via #1295)v3.7.0Compare Source
Interface changes:
v2OperationIdCompatibilityModeoption is now available. You can use it to generate v2-style names for operations in the tags interface.Changelog:
v3.6.0Compare Source
Interface changes: you can now return a Promise from a
requestInterceptororresponseInterceptorand Swagger-Client will wait for it to resolve.Changelog:
n > 1rounds of subtree resolution (via #1274)v3.5.2Compare Source
Interface changes: none.
Changelog:
$ref: "./myOtherDoc.json") are no longer erroneously flagged as indirect circular references (via #1265)v3.5.1Compare Source
Interface changes: none.
Changelog:
mergeDeepJSON patches now intelligently take shortcuts if source and destination object properties do not conflict (via #1217)fast-json-patch@2, which solves an issue that was blocking React Native users from using the library (via #1253)v3.5.0Compare Source
Interface changes: Added
Swagger.resolveSubtree.Changelog:
v3.4.11Compare Source
FYI:
3.4.10was mistakenly built from an older commit during3.4.9's deploy process, so3.4.11was released to supersede them both.Interface changes: none.
Changelog:
$refandallOfparsing (via #1195)v3.4.10Compare Source
v3.4.9Compare Source
v3.4.8Compare Source
Interface changes: none.
$$refmeta patches are no longer erronously attached to $ref targets (via #1237)style: deepObjectis now built correctly (via #1235)http.withCredentialsflag is now correctly applied (via #1236)v3.4.7Compare Source
Interface changes: none.
shouldDownloadAsTextlogic (via #1227)withCredentialsflag now works as expected (via #1189)v3.4.6Compare Source
Interface changes: none.
application/yamlis now advertised as an acceptable media type when fetching remote decoments (via #1232)__originalOperationIdis now more performant and accurate (via #1225)v3.4.5Compare Source
Interface changes: none.
- 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.v3.4.4Compare Source
Interface changes: none.
$refkeys in freely-named key positions within the Swagger/OpenAPI specification (via #1214)v3.4.3Compare Source
Interface changes: none.
v3.4.2Compare Source
Interface changes: none.
Version diff
v3.4.1Compare Source
Interface changes: none.
formatValuenow handles OAS3 parameter values correctly (via #1200)Version diff
v3.4.0Compare Source
Interface changes: none.
servers(via #1192)style/explode/allowReservedsubsystem: generated requests that use those options should be more accurate now (via #1193)Version Diff
v3.3.5Compare Source
Interface changes: none.
application/x-www-form-urlencodedrequest bodies are now stringified and escaped correctlyVersion Diff
v3.3.4Compare Source
Interface changes: none.
JSON.parse/JsYaml.safeLoadswitching logic, it's now easier to slim down Swagger-Client if you don't need YAML parsing (via #1183)Version Diff
v3.3.3Compare Source
Interface changes: none.
allowReservedprocessing (via #3817)Version Diff
v3.3.2Compare Source
Interface changes: none.
isomorphic-fetchtocross-fetch(via #1158)build-devscript that creates non-minified dist files (via #1172)Version Diff
v3.3.1Compare Source
Interface changes: none.
Version Diff
v3.3.0Compare Source
Interface changes: none.
bearertoken types are no longer case-sensitive, and will always result in aBearerprefix in the Authorization header (via #1156)serversdefined no longer cause TypeEerrors when trying to execute (via #1160)requestInterceptorandresponseInterceptoroptions now intercept definition and $ref download requests (via #1161)fetch-mock's version, since they patched a release that broke our tests (via #1162)Version Diff
v3.2.2Compare Source
Interface changes: none.
fetch-mockdevDependency version constraints, to fix a problem with a new version that was breaking our builds (via #1148)startsWiththat was causing IE11 problems (via #1153)Version Diff
v3.2.1Compare Source
This release contains no source changes; it constrains
fast-json-patch's version in order to avoid noisy warnings present in their latest versions.v3.2.0Compare Source
Interface changes: none.
styleandexplodeis now supported within OpenAPI 3.0 definitions (via #1140)contextUrls are now properly considered for OpenAPI 3.0 requests (via #1141)Version Diff
v3.1.2Compare Source
Interface changes:
${in}.${name}as well as by name.Version Diff
v3.1.1Compare Source
Interface changes: None
allOfhandling, so original values are preserved (via #1130, fixes many related UI bugs)access_tokenvalues no longer create an empty Authorization value (via #1131)v3.1.0Compare Source
Interface changes: None
v3.0.20Compare Source
Interface changes: None.
Version Diff
v3.0.19Compare Source
Interface changes: None.
propertieskeyword as property name (swagger-api/swagger-ui#3376 via #1108)Version Diff
v3.0.18Compare Source
Interface changes: None.
allOfconstructs (via #1101)0values (via #1105)v3.0.17Compare Source
v3.0.16Compare Source
Interface changes: None.
Array.prototype.find(via #1088)falsewere not being properly serialized in buildRequest (via #1093)Version Diff
v3.0.15Compare Source
Interface changes: None.
package-lock.jsonfrom the repository, as it was causing problems.Version Diff
v3.0.14Compare Source
Interface changes: None.
__originalOperationIdlogic (swagger-api/swagger-ui#3203) and added more tests around the functionalityVersion Diff
v3.0.13Compare Source
v3.0.12Compare Source
Interface changes: New resolve options, see below.
parameterMacroandmodelPropertyMacrooptions inresolve(via #1067)Version diff
v3.0.11Compare Source
v3.0.10Compare Source
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.
get_oneinstead ofget-/one), and duplicate explicit operationIds are now handled more reliably (#1003 via #1048)formData+ fix multipart upload (via #1051)Version Diff
v3.0.9Compare Source
Interface changes: no longer need to manually stringify request bodies for execute.
Authorization: Bearer ...in OAuth2, for RFC 6750 compliance (#1040 via #1041)responseproperty on Errors (via #1039)Version Diff
v3.0.8Compare Source
Interface changes: Potentially breaking change for corner cases to internal
fetch. We elected to break semver for this release - see discussion in #1015.baseDocis present (via #1031)Version Diff
v3.0.7Compare Source
v3.0.6Compare Source
v3.0.5Compare Source
v3.0.4Compare Source
v3.0.3Compare Source
Interface changes: No runtime interface changes, but the bundle file is now exported as a UMD module.
loadSpecoption tofetchthat allows optimistic loading of a resource as text, regardless of responseContent-TypeexecutecontextUrloption that allows user to specify the URL that a spec is in the context ofVersion Diff
v3.0.2Compare Source
Interface changes: None
Access-Control-Allow-Origin: *header is no longer attached to all requestsVersion Diff
v3.0.1Compare Source
All new! The swagger-js project has been completely rewritten to clean up the code base as well as prepare for the upcoming OpenAPI Specification 3.0 (OAS 3.0).
Please note that the library does not currently support OAS 3.0 as it is still in draft form.
Expect an update to this library as we approach the release.
We have worked hard to improve the library without breaking too many plates along the way.
With progress comes change, though, and there are a number of changes that you need to carefully consider before upgrading to this version.
Depending on your programming techniques, the upgrade could have zero impact on your usage of the library.
Breaking changes
In releasing the 3.x series of swagger-js tooling, we have made extensive changes to how to interact with the library.
If you cannot support these changes, please remain on the 2.x series!
The changes are listed below.
You now must use node 6.x to build the swagger-js project. This is due to the standardization on ES6 syntax, among other things.
Note, newer versions may work fine, but the project is built and tested with 6.x.
Minimum browser support: es5 compatible. IE11+ ( can probably make it run in IE10 )
Minimum runtime node version: 4.x
The constructor is similar, but there are some key differences.
var promise = Swagger({...}).then(client => { ...} )Swagger Specification
1.0,1.1,1.2are no longer supported. Please remain on the 2.x series if you need to use older specification versions.Promise-only support. The older callback/error function signatures have been dropped to allow for a modern and consistent promise pattern.
qlibraray in favour of the more standard approach of using native promises and a pollyfill where needed.Dropped all rendering logic. During the evolution of swagger-js, there was some rendering logic in the project for legacy support. Well that's gone now, and there is a clear separation of concerns between parsing & execution (swagger-js) and rendering (swagger-ui + others).
Dropped
asCurlfrom library. This was considered to be part of rendering logic and removed with the reasoning above.Major changes
Instantiation of swagger-js supports the 2.x series, with the exception that
usePromiseis implicitly (and always) true.New instantiation structure example:
Swagger({ ... }).then( client => { ... }), whereclienthas all the goodies.Static functions, can do everything the methods can.
Code structure. There is now a clear separation between execution, resolution, and public interfaces.
Test structure, using http mocks instead of real nodejs servers. Much faster.
New build system, webpack + babel
More details...
Can be seen in Migration from 2.x.
Known limitations
There are some items which are limitations with the current release but are planned to be included to the library. Want them faster? Consider upvoting issues and being patient. Or even better, jump in and contribute!
Several internals to swagger-js 2.x ( see the the Graveyard.
Macro support
Global defaults for executing operations. Beyond the defaults described by the specification. Completely dropped
Authentication. Limited support exists for try-it-out requests, none for the fetching of the OAS specs. This is a high priority and is being tracked in issues.
Renovate configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻️ Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "
rebase!".🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.