* use request body schema `required` for marking required urlencoded properties
* don't use sample schema value as a fallback
* modify property layout to mimic regular parameters
* clean up
* use default or example for iniital values
* add tests for example feature
* refactor ParameterRow value setter logic
* aside: fix property access in sampleFromSchema
* prioritize media type examples for OAS3 responses
* use `example` in schema level example
* refactor: move stringify to utils
* prioritize media type examples in OAS3 request bodies
* modify nightwatch config
* fix parameter/response regressions
* reorder and broaden default value sources
* update lockfile
* fix(validator-badge): resolve definition URLs against browser location
* use param as meta parameter if not found
* convert request body from Immutable if necessary
* show file upload for `format: binary` and `format: base64` jsonschema strings
* add `dispatchInitialValue` prop to JsonSchemaForm
* add optional subkey parameter to onChange
* add binary media type support to request body
* http-auth: Include unsupported scheme name in error message
* http-auth: Treat authentication scheme case insensitively
The spec refers to RFC 7235 for scheme names, and the RFC says names
are matched case insensitively.
* linter fixes
* 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
* 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
* Remove produces/consumes setter from OperationContainer
* Store consumes/produces information in `meta` key
* Migrate produces value state usage to `meta` key
* use meta consumes data for isXml check
* Fix failing tests
* normalize action name casing
* restore correct produces fallback value logic
* default to first server if current server is invalid
...don't already have a currentServer.
This avoids having the selected server reset each time the
operation is expanded, or the Try-It-Out mode is entered.