Open karenetheridge opened 4 years ago
see also this thread. https://app.slack.com/client/T5CHC2TAN/CT8QRGTK5/thread/CT8QRGTK5-1589687250.289900
thread captured here before the scrollback vanishes: https://www.dropbox.com/s/w08yp1u8ziu8wqh/Screen%20Shot%202021-07-19%20at%2009.24.10.png?dl=0
my additions part 2:
(and if the type of an instance is restricted to things that aren't object or array, 'default' makes no sense at all, because a missing item will never get the annotation - it only makes sense for non-scalar types)
properties
adjacent to a type: string
and see the additions we can do for openapi linting: https://github.com/karenetheridge/OpenAPI-Modern/issues/59
It has been brought up on slack that a "lint" feature would be useful - this would look for potential problems in as schema that, while they are legal syntax, are generally nonsensical constructs. This would include missing keywords, or keywords used in strange combinations with each other.
From @ssilverman:
my additions:
$ref
used as a property name rather than a keyword (this will of course produce a false positive in metaschemas)$schema
used in a subschema where there is not an$id
(this should perhaps be promoted into the metaschema itself)@notEthan's ideas (warnings, not errors):