-
Notifications
You must be signed in to change notification settings - Fork 9.1k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #4137 from ralfhandl/schemas-yaml-to-json-test-che…
…ck-in Run tests with YAML metaschemas
- Loading branch information
Showing
12 changed files
with
100 additions
and
3,243 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,16 +1,30 @@ | ||
OpenAPI 3.0.X JSON Schema | ||
--- | ||
# OpenAPI 3.0.X JSON Schema | ||
|
||
Here you can find the JSON Schema for validating OpenAPI definitions of versions 3.0.X. | ||
Here you can find the JSON Schema for validating OpenAPI definitions of versions 3.0.x. | ||
|
||
As a reminder, the JSON Schema is not the source of truth for the Specification. In cases of conflicts between the Specification itself and the JSON Schema, the Specification wins. Also, some Specification constraints cannot be represented with the JSON Schema so it's highly recommended to employ other methods to ensure compliance. | ||
As a reminder, the JSON Schema is not the source of truth for the Specification. | ||
In cases of conflicts between the Specification itself and the JSON Schema, the | ||
Specification wins. Also, some Specification constraints cannot be represented | ||
with the JSON Schema so it's highly recommended to employ other methods to | ||
ensure compliance. | ||
|
||
The iteration version of the JSON Schema can be found in the `id` field. For example, the value of `id: https://spec.openapis.org/oas/3.0/schema/2019-04-02` means this iteration was created on April 2nd, 2019. | ||
The iteration version of the JSON Schema can be found in the `id` field. | ||
For example, the value of `id: https://spec.openapis.org/oas/3.0/schema/2019-04-02` means this iteration was created on April 2nd, 2019. | ||
|
||
To submit improvements to the schema, modify the schema.yaml file only. | ||
## Contributing | ||
|
||
To submit improvements to the schema, modify the `schema.yaml` and add test cases for your changes. | ||
|
||
The TSC will then: | ||
- Run tests on the updated schema | ||
- Update the iteration version | ||
- Convert the schema.yaml to schema.json | ||
- Publish the new version | ||
|
||
## Tests | ||
|
||
The [test suite](../../tests/v3.0) is part of this package. | ||
|
||
```bash | ||
npm install | ||
npm test | ||
``` |
Oops, something went wrong.