* fix(auth): improper resolution of relative token urls
* revert cc58ba7 for OAS2
In OAS2, relative token URLs are resolved against the host that serves the specs.
* Adding enum values for Enum Type in Swagger ReadOnly documentation
* Adding enum values for Enum Type in Swagger ReadOnly documentation (optimisation) and also adding default/example value
* Add new display enums, defaults, and examples when not in TIO mode (another way to have enums values in swagger.json)
* Fix npm test result
* review corrections
* fix: don't render parameter description if field is empty
* use cross-version schema variable to access properties
* pass className through Markdown component usage
* add per-field classNames to Markdown for easier styling + testing
* remove parameter Example field (out-of-scope for this PR)
* get default value from schema instead of top-level parameter
* tests: add e2e cases for swagger2 and oas3
* remove `swagger-petstore-enum.json`
the purpose of this file lives on in the e2e test specs folder
* add missing proptypes validation
* use `classnames` to more effectively union class names
* test(e2e): modify e2e hot server to peacefully coexist with dev server
* tests: add failing e2e test case
* fix: use originalOperationId for layout targeting, if available
* fix(dev-server): don't open localhost in a browser
* tests: refactor model-example enzyme tests to be more isolated
* tests: add failing sampleFromSchema tests for $$ref keys
* tests: add additional test for user-created $$ref values
* fix: create deeplyStripKey; use it to filter $$refs out of examples
* tests: add cases for deeplyStripKey
* WIP: trigger resolution of Path Item $ref on spec load
* fix(dev-server): don't open localhost in a browser
* preserve key order when merging specJson with specResolvedSubtrees
* remove stray `debugger`
* improve: show possible reasons when url fetch fails
* Only check for fail reasons if no HTTP status code
* Check for mixed content errors first
* Harmonise error messages
* Set error source to 'fetch'
* improve: hide loading validator image (#4287)
* hide missing validator image
* Render nothing if validator badge has not loaded/received errors
* Revert style changes
* Allow images with data scheme (#4305)
* Add UnitTest for image
allows image elements with https scheme
* Test images with data scheme
* Add allowedSchemesByTag
* Fix error Strings must use doublequote quotes
* Add empty div (#4236)
if there are properties show an empty div
* v3.12.1 (#4311)
* v3.12.1
* Rebuild dist for v3.12.1
* Use window wrapper instead of direct reference
* Add trailing period to error messages
* improve readability
* Add UnitTest for images
allows image elements with https scheme
* Test images with data scheme
* Add allowedSchemesByTag
* Fix error Strings must use doublequote quotes
* Use `parameterWithMeta` to get parameter data in <ParameterRow>
* Prefer specPath when fetching resolved subtrees in OperationContainer
* Add test for OAS3 callback rendering
* Remove debugger statement
* Pass base resolution URL directly to Swagger-Client subtree resolver
* Remove accidental comment
* Migrate additional options
* Don't default to empty Map when getting subtree
* fix(validateParam): check for ImList type before using count method
* Use `replaceState` to update `urls.primaryName`
This gives us the stateful URL we want, without:
(a) refreshing the page on update
(b) creating a long, useless history for the user
(c) implying that browser history is two-way bound
to Swagger-UI (it isn't, we don't have a router)
* Add `fn.opsFilter` docs and internal API versioning note
* restrict `x-example` functionality to Swagger 2.0
* polish Authorize + Close buttons
* add tachyons; use it for padding the new Reset button
* v3.12.0
* rebuild dist
* Add a button to reset example when user modifys request body
* lint fixes
* Revert "lint fixes"
This reverts commit 5395005ea775832045aee9bab4aaa538cd2f73ab.
* reapply lint fixes
* Read the x-example field and use them as values
Allow to show the value defined in the "x-example" field when pressing try-out. The "default" value will have the precedence over the x-example
* Use `parameterWithMeta` to get parameter data in <ParameterRow>
* Prefer specPath when fetching resolved subtrees in OperationContainer
* Add test for OAS3 callback rendering
* Remove debugger statement
* Pass base resolution URL directly to Swagger-Client subtree resolver
* Remove accidental comment
* Migrate additional options
* Don't default to empty Map when getting subtree
* make "default" and "x-example" mutually exclusive
"x-example" wins when both are present
* limit "x-example" to non-body parameters
* Use `parameterWithMeta` to get parameter data in <ParameterRow>
* Prefer specPath when fetching resolved subtrees in OperationContainer
* Add test for OAS3 callback rendering
* Remove debugger statement
* Pass base resolution URL directly to Swagger-Client subtree resolver
* Remove accidental comment
* Migrate additional options
* Don't default to empty Map when getting subtree
* Use `parameterWithMeta` to get parameter data in <ParameterRow>
* Prefer specPath when fetching resolved subtrees in OperationContainer
* Add test for OAS3 callback rendering
* Remove debugger statement
* Pass base resolution URL directly to Swagger-Client subtree resolver
* Remove accidental comment
* Migrate additional options
* Use `parameterWithMeta` to get parameter data in <ParameterRow>
* Prefer specPath when fetching resolved subtrees in OperationContainer
* Add test for OAS3 callback rendering
* Remove debugger statement
