- Fix location of py.typed file
- Add py.typed marker - PR #158
- Enforce python_requires>=3.7
- Add type annotations - PR #157
- Drop py2 and py36 support - PR #157
- Drop simplejson - PR #157
- Make checks for unique operation ids global instead of per tag - PR #145
- Fix recursive ref resolution for some specs split across multiple files - PR #140
- Fix recursive definition detection - PR #139
- Fix: additionalProperties can be a boolean value - PR #138
- Ensure correct validation into additionalProperties and items specifications - PR #134. Thanks brycedrennan for your contribution.
- Improve validation performance in case of consecutive validations. - PR #132. Thanks brycedrennan for your contribution.
- Use
yaml.CSafeLoader
if available - PR #122 - Show definition name when raising
SwaggerValidationError
- PR #124
- Fix regression, introduced by PR #111, that was causing descending references with no scope. - PR #113
- Add warning when
$ref
is defined to haveNone
value - PR #111 - Ensure that only valid references (
$ref
attribute is present with string value) are dereferenced - PR #111
- Add warning when using
$ref
together with other properties - PR #107
- Disallow multiple types in schema definitions. See OpenAPI#458 for context - PR #106
- Fix urlopen issue on Windows platform. Issue #99, PR #101
- Ensure that inline models are validated - #97
- Ensure that parameters are validated - #97
- Validation of defaults set to None is skipped if x-nullable is set - #97
- Add support for reading YAML files - #74
- Make sure operationIds are unique within the same tag - #93
- Validate that array models in the top-level definitions have an
items
property (validation for array models in other places will come in a future release) - #95 - Responses (the mapping of HTTP status codes to Response objects) cannot be a reference - #92
$ref
values need to be strings - #83. Thanks ceridwen for your contribution!- Ensure that default values are compliant with the spec - #82
- More helpful error message when encountering unresolvable path params - #72. Thanks daym for your contribution!
- Properly validate polymorphic objects - #68
- Rename package to swagger-spec-validator to fix PyPI upload issues - #59
- Ignore x- vendor extensions in the schema at the #/paths/{path}/{http_method} level - PR #45
- Swagger 2.0 schema synced with upstream - PR #40
- Fix regression with Swagger 1.2 schemas - #43
- Fix rich validations that rely on a working deref with scope annotations
- Support for recursive $refs
- Unqualified $refs no longer supported.
Bad:
{"$ref": "User"}
Good:{"$ref": "#/definitions/User"}
- Workaround for validation of Swagger 2.0 schemas with external refs - #38
- Validate crossrefs - #33, #34
- Handle API level parameters - #29
- More robust handling of $refs - #29
- Validation for model name and it (Swagger 1.2)
- Remove unnecessary dependency on pyyaml
- Pin of jsonschema used for unit tests for Python3
- Sync Swagger 2.0 schema with upstream - allow empty arrays for parameter
- Handle schemas with no definitions
- Petstore URLs updated
- Support 'type: File' for (Swagger 1.2)
- Python3 support
- Use simplejson when available
- Add file:// support
- Initial support for Swagger 2.0
- Bugfix for path construction in validate_resource_listing_url
- Bugfix to including jsonschema files
- Initial version