Update dependency swagger-ui to v3.23.11 - autoclosed #51
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:
3.2.2
->3.23.11
By merging this PR, the issue #45 will be automatically resolved and closed:
Release Notes
swagger-api/swagger-ui
v3.23.11
Compare Source
Changelog
@import
chaining" vulnerability (via #5616)v3.23.10
Compare Source
This release fixes two bugs: one visual issue within static documentation, and another within runtime validation for Array-typed parameters.
Changelog
<Select disabled>
fortype: string
+enum
schemas (#5601)v3.23.9
Compare Source
This release changes the default value for the
validatorUrl
configuration option fromhttps://online.swagger.io/validator
tohttps://validator.swagger.io/validator
.v3.23.8
Compare Source
This release fixes an issue with Swagger 2.0 required body parameter runtime validation (#5583) that was introduced in v3.23.7.
v3.23.7
Compare Source
This release includes new support for display and Try-It-Out functionality of OAS 3.0
Parameter.content
values.Changelog
Parameter.content
(#5571)43db164
2019-08-27 | docs: clarify that preauthorizeApiKey works for OAS3 Bearer auth too (#5566)v3.23.6
Compare Source
This release fixes a React warning originating in Swagger UI and a CSS class name collision with Bootstrap 4.0.
It also includes several in-range updates to minimum dependency versions.
Changelog
.col
class that causes collision with Bootstrap (via #5541)v3.23.5
Compare Source
This release includes a fix to our Markdown parsing implementation that should resolve display issues with certain Markdown strings.
Changelog
v3.23.4
Compare Source
Changelog
@kyleshockey/js-yaml
->js-yaml
(via #5511)npm audit
resolutions (via #5509)v3.23.3
Compare Source
This release resolves an undeclared dependency issue visible in
[email protected]
due to usage of@babel/runtime-corejs2
. No source changes were made.See #5505 for more information.
v3.23.2
Compare Source
This release includes improvements to our Docker container permissions, bug fixes for OpenAPI 3.0 rendering of Responses and Request Bodies, and resolution of most
npm audit
warnings visible to consumers.Channgelog
content
(via #5504)null
as a notSetValue for examplesForMediaType (via #5503)npm audit
warnings (via #5457)v3.23.1
Compare Source
This release fixes a couple of minor regressions introduced in v3.23.0, and also includes improvements to our module sizes and sourcemap quality.
Changelog
Response.examples
(via #5464 + #5465)Note:
[email protected]
was unpublished due to a bad build being pushed to npm. It will be updated again with the next release of Swagger UI.v3.23.0
Compare Source
This release includes support for OpenAPI 3.0's Examples Object within Parameter, Request Body, and Response Objects.
Changelog
Internal API notes
Several things have moved around internally.
If you make heavy use of the Plugin API, this may be of concern to you:
Parameters
component no longer has awrapComponent
in OpenAPI 3.0. Version-specific logic is now contained within one component.ParameterRow
now needsoas3Actions
andoas3Selectors
as props.Response
now needspath
andmethod
as props.Responses
'shouldComponentUpdate
check has been removed, it now re-renders as the Redux store changes.RequestBodyEditor
has been heavily modified. It is no longer aware of the underlying request body or schema, and only concerns itself with the string value being edited. It will now also update its own internal state if thevalue
prop given to it changes.v3.22.3
Compare Source
No source changes.
This release moves Swagger UI to
[email protected]
.v3.22.2
Compare Source
Changelog
isShown
check to 's propexpanded
logic (via #5331)v3.22.1
Compare Source
[email protected]
lacked the changes that were advertised for it in that version - specifically,docExpansion
support was missing.[email protected]
is now available with the new changes. See #5294 for more information.Changelog
v3.22.0
Compare Source
This release introduces a new configuration option (
withCredentials
) which allows control of Swagger UI's underlying Fetch/XHR instance's credential inclusion mode. You may find this option helpful if your API requires an authentication/authorization scheme that Swagger UI doesn't directly support, but can be handled out-of-band by your browser.Also notable: GitHub Flavored Markdown table syntax is now supported in our OpenAPI 3 Markdown parser,
swagger-ui-react
's underlying UI system object is now exposed in theonComplete
prop callback,react-addons-perf
is removed from our dependencies to avoid BSD+Patents licensing, and we've improved how Markdown is rendered across Swagger UI.Changelog
withCredentials
configuration key (via #5149)v3.21.0
Compare Source
This release marks the introduction of a new flavor of Swagger UI:
swagger-ui-react
.This new module exports a component for use in React applications, and allows you to use any React version you'd like, without fear of colliding with Swagger UI's internal React version.
We recommend that anyone using Swagger UI within a React application migrate to this module, instead of continuing to mount Swagger UI onto a React-created DOM node by ID.
This release also includes some fixes that improve Swagger UI's handling of rare edge cases in the resolver engine.
Note: this release was also erroneously pushed out as
v3.20.10
- both versions' contents are identical.Changelog
swagger-ui-react
module (via #5207)v3.20.10
Compare Source
v3.20.9
Compare Source
This release contains a security fix that addresses a cross-site scripting vulnerability. If you use Swagger UI to display untrusted OpenAPI documents, you should upgrade to this version ASAP.
This release also changes Swagger UI's
OperationSummary
component to better tolerate badly-formed (i.e., non-string)summary
fields.Changelog:
v3.20.8
Compare Source
Summary
This release contains styling fixes, support for
x-www-form-urlencoded
bodies without explicitly-defined request properties, and non-material security fixes from upstream modules.In order to take advantage of the new
X-Requested-With
header in OAuth2 token requests, cross-origin APIs (which require CORS configuration) needs to sendAccess-Control-Allow-Headers: X-Requested-With
as part of the OPTIONS response for your token endpoint. A CORS library will handle this for you - visit https://enable-cors.org for more guidance.Changelog
X-Requested-With
to prevent browser authentication dialog (via #4934)v3.20.7
Compare Source
Interface changes: none.
Changelog:
url
remote document load ifurls
is provided (via #5161)v3.20.6
Compare Source
Interface changes: none.
Changelog:
allowEmptyValue
+required
interactions (via #5142)v3.20.5
Compare Source
Interface changes: None.
Changelog:
v3.20.4
Compare Source
Interface changes: none.
Changelog:
urls.primaryName
functionality regression (via #5097)v3.20.3
Compare Source
Interface changes: none.
Changelog:
v3.20.2
Compare Source
Interface changes: none.
Changelog:
Schemas
in OpenAPI 3 (via #5065)v3.20.1
Compare Source
Private interface changes:
specSelectors.operationConsumes
was removed in favor of the newspecSelectors.consumesOptionsFor
selector.Changelog:
v3.20.0
Compare Source
Interface changes: none.
Changelog:
.js
->.jsx
file extensions (via #5014)v3.19.5
Compare Source
Interface changes: A handful of Docker environment variables were added and deprecated, see #4965 and #4987 for more information.
Changelog:
xml
fork (via #4985)v3.19.4
Compare Source
Interface changes: whitespaced tags and operation IDs are now percent-encoded when included in deep links. Links generated by older 3.x versions of Swagger UI should continue to work as before, but support for them will be dropped in the next major version of Swagger UI.
Changelog:
Additional work around deep linking was also made in #4960 and #4958.
v3.19.3
Compare Source
This release was made specifically to fix inconsistent plugin behavior related to multiple invocations of Swagger UI, which was patched in #4923.
v3.19.2
Compare Source
This release fixes a regression (#4912), in which some OpenAPI 3 definitions would not have their Servers block rendered.
v3.19.1
Compare Source
Interface changes: none.
Changelog:
v3.19.0
Compare Source
Interface changes: added
CONFIG_URL
option for Docker image.Changelog:
v3.18.3
Compare Source
Interface changes: none.
Changelog:
test
script (via #4847)v3.18.2
Compare Source
Interface changes: none.
Changelog:
v3.18.1
Compare Source
Interface changes: none.
Changelog:
v3.18.0
Compare Source
Interface changes:
rel="noopener noreferrer"
, which blocks linked pages from accessingwindow.opener
and theReferrer
header.Changelog:
allowEmptyValue
parameters (via #4788)updateJsonSpec
wrap-action (via #4785)v3.17.6
Compare Source
Interface changes: none.
Changelog:
v3.17.5
Compare Source
Interface changes: none.
Changelog:
v3.17.3
Compare Source
Interface changes: none.
Changelog:
v3.17.2
Compare Source
Interface changes: none.
Changelog:
v3.17.1
Compare Source
Interface changes:
BaseLayout
was changed - if you've copied it into your application, you can copy over the new, simplified version.Changelog:
v3.17.0
Compare Source
Interface changes: none.
Changelog:
urls
configuration via docker (via #4601)<OperationTag>
(via #4349)v3.16.0
Compare Source
Interface changes: none.
Changelog:
npm start
script (via #4572)v3.15.0
Compare Source
Interface changes: Docker images are now tagged without a leading
v
, e.g.3.15.0
instead ofv3.15.10
.Changelog:
v
from Docker image names (via #4567)v3.14.2
Compare Source
Interface changes: none.
Changelog:
title
prpoerty as the name for a model, if it is available (via #4542)v3.14.1
Compare Source
Interface changes: none.
Changelog:
dompurify
(via #4513)v3.14.0
Compare Source
Interface changes: added
showCommonExtensions
option.Changelog:
showCommonExtensions
option to showpattern
,minLength
,maxLength
,minimum
, andmaximum
fields for Parameters (via #4245)v3.13.6
Compare Source
Fixes a regression related to parameter normalization that was causing an infinite loop; see https:/swagger-api/swagger-ui/issues/4466 and https:/swagger-api/swagger-ui/issues/4467.
v3.13.5
Compare Source
Interface changes: none.
Changelog:
v3.13.4
Compare Source
Interface changes: you no longer need to include the
<svg>
tag in your HTML when you run Swagger-UI - the SVG data is now bundled in with the rest of the app!Changelog:
<Schemes>
select list through Redux application state (via #4436)v3.13.3
Compare Source
(released on Friday, April 6, 2018)
Interface changes: you can now return a Promise from a
requestInterceptor
orresponseInterceptor
and Swagger-UI will wait for it to resolve.Changelog:
enum
anddefault
in documentation (via #4191)additionalQueryStringParams
option (via #4419)v3.13.2
Compare Source
Interface changes: none.
Changelog:
MAINTAINER
usage toLABEL
(via #4370)v3.13.1
Compare Source
Interface changes: none.
Changelog:
spec
anddocExpansion
options now work together (via #4358)example
keys are no longer placed in model displays for examples (via #4365)v3.13.0
Compare Source
Interface changes: Added
onComplete
config option;preauthorizeApiKey
andpreauthorizeBasic
instance methods.Changelog:
onComplete
config option (#4322)InfoUrl
andInfoBasePath
(#4330)v3.12.1
Compare Source
Interface changes: none.
Changelog:
data:
scheme (via #4236)v3.12.0
Compare Source
Interface changes: none.
Changelog:
x-example
fields and use them as initial values (via #3538)urls
anddeepLinking
options now play well together, by usinglocation.replaceState
to update theurls.primaryName
setting in the browser query string (via #4181)filter
is now housed within a plugin, which allows custom filtering logic through the plugin system (via #4255)anyOf
andoneOf
(via #4136)consumes
value regression (#4265)baseDoc
to Swagger-Client (via #4273)[email protected]
to solve a fatal error experienced by a small subset of users (via #4270)v3.11.0
Compare Source
This release includes significant improvements to Swagger-UI's performance. The concept of an entirely-resolved spec representation has been done away with in favor of resolved subtrees: as the user expands operations and models in Swagger-UI, work is done to resolve only the parts needed for display. This allows us to do initial renders more quickly and paves the way for a more responsive editing experience in Swagger-Editor.
As a result, there are some breaking changes to various private APIs (mostly
spec
facilities that focus on the resolved state). If you run custom plugins that rely on that data, you'll want to check for compatibility before upgrading.As a reminder: breaking private API changes result in a minor version bump, not a major bump.
Interface changes:
defaultModelsExpandDepth
behavior has changed; the default1
value now leaves all models collapsed for performance reasons related to the new lazy resolution.specResolved
is no longer updated by default; plugins that rely on it should move tospecJson
orspecJsonWithResolvedSubtrees
.Changelog:
lodash
dependency due to potential vulnerability (via #4224)v3.10.0
Compare Source
Interface changes: added
supportedSubmitMethods
option to public API.Changelog:
supportedSubmitMethods
option for disabling Try-It-Out based on operation method (via #4186)v3.9.3
Compare Source
Interface changes: none.
v3.9.2
Compare Source
Interface changes: none.
urls
option to be specified in Docker (via #4044)Content-Disposition: attachment
priority overContent-Type
when choosing to display or offer download of a response (via #4140)OperationContainer
(via #4137)border-box
box styling in main stylesheet (via #4121)v3.9.1
Compare Source
Interface changes: none.
swagger.json
can be modified within the container (via #4024)swagger-ui
npm module now includes Standalone Preset (via #4101)format: uuid
is no longer case-sensitive (via #4102)v3.9.0
Compare Source
Interface changes: one core plugin API change, no public API changes.
Introduced a breaking function signature change to
errActions.newThrownErr
action creator (from(err, action)
to(err)
) anderr_new_thrown_err
action payload (stopped nesting error content undererror
key in payload, now the error is the payload).console.error
and walk down the stack to see what's going wrong.hasOwnProperty
checks to a handful offor...in
loops (via #4043)location
to set Docker base url instead of moving things around the filesystem (via #4073)Promise
on global/window object, which makes IE11 a very happy browser (via #4077)zopflipng
to compress PNG assets in repo (via #4037)v3.8.1
Compare Source
this
binding toafterLoad
plugin interface to expose raw plugin context (via #4059)specPath
inequality (via #4060)v3.8.0
Compare Source
Interface changes:
afterLoad
method in order to make changes to the top-level system after the plugin is merged into the system.initialState
parameter now allows removal of default keys by setting its value toundefined
in the parameter.afterLoad
plugin