json-schema-org/json-schema-linting

Issues

• Test suite(s)

  #19 opened 2 years ago by gregsdennis
  1

• Require `$id`

  #16 opened 2 years ago by gregsdennis
  1

• Require `$schema` at the root

  #17 opened 2 years ago by gregsdennis
  0

• Suggest meta-data like `title`, `description`, etc.

  #15 opened 2 years ago by gregsdennis
  0

• Suggest `min*`/`max*` in appropriate cases

  #14 opened 2 years ago by gregsdennis
  0

• Suggest `type` with the right value based on the adjacent keywords

  #10 opened 2 years ago by gregsdennis
  0

• Range validation

  #13 opened 2 years ago by gregsdennis
  0

• Values in `default` and `examples` do not match the local subschema

  #12 opened 2 years ago by gregsdennis
  0

• Version-specific rules?

  #11 opened 2 years ago by gregsdennis
  0

• Contradictory types between a keyword and a subschema of an adjacent applicator

  #9 opened 2 years ago by gregsdennis
  0

• Properties listed in `required` should be declared in `properties`

  #8 opened 2 years ago by gregsdennis
  0

• Unknown `format` values should be flagged

  #7 opened 2 years ago by gregsdennis
  0

• `minContains` or `maxContains` without `contains` is unnecessary

  #6 opened 2 years ago by gregsdennis
  0

• `if` without `then` or `else` (and vice versa) is unnecessary

  #5 opened 2 years ago by gregsdennis
  0

• `additionalItems` adjacent to schema-form `items` is unnecessary

  #4 opened 2 years ago by gregsdennis
  0

• Disallow `$schema` unless an object is a resource root (has `$id`)

  #3 opened 2 years ago by gregsdennis
  0

• Validation keywords that don't operate on the specified type should be removed

  #2 opened 2 years ago by gregsdennis
  0

• `enum`/`const` do not require additional validation

  #1 opened 2 years ago by gregsdennis
  0