Giters
json-schema-org
/
json-schema-linting
Linting tools to help build better JSON Schemas
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
7
Watchers:
6
Issues:
18
Forks:
0
json-schema-org/json-schema-linting Issues
Test suite(s)
Updated
2 years ago
Comments count
1
Require `$id`
Updated
2 years ago
Comments count
1
Require `$schema` at the root
Updated
2 years ago
Suggest meta-data like `title`, `description`, etc.
Updated
2 years ago
Suggest `min*`/`max*` in appropriate cases
Updated
2 years ago
Suggest `type` with the right value based on the adjacent keywords
Updated
2 years ago
Range validation
Updated
2 years ago
Values in `default` and `examples` do not match the local subschema
Updated
2 years ago
Version-specific rules?
Updated
2 years ago
Contradictory types between a keyword and a subschema of an adjacent applicator
Updated
2 years ago
Properties listed in `required` should be declared in `properties`
Updated
2 years ago
Unknown `format` values should be flagged
Updated
2 years ago
`minContains` or `maxContains` without `contains` is unnecessary
Updated
2 years ago
`if` without `then` or `else` (and vice versa) is unnecessary
Updated
2 years ago
`additionalItems` adjacent to schema-form `items` is unnecessary
Updated
2 years ago
Disallow `$schema` unless an object is a resource root (has `$id`)
Updated
2 years ago
Validation keywords that don't operate on the specified type should be removed
Updated
2 years ago
`enum`/`const` do not require additional validation
Updated
2 years ago