Switch to if/then style for context properties#150
Conversation
|
... to provide better error-reporting when using general-purpose JSON Schema validators.
gnidan
changed the title
Added some logic to do custom rendering for this kind of schema. This is modeled after how I did the pointer collection schema, although this might be overkill. Will try to simplify a bit before merging. |
|
Regarding the concern raised in my previous comment here, I considered an alternative approach: just define context properties the normal object way, i.e., type: object
properties:
code:
$ref: "schema:ethdebug/format/materials/source-range"
# ... etc.This is functionally the same thing as the current state of the schema, but it would require removing the outer wrapping from each of the context types, which are defined in separate schema files. I am apprehensive about this, because I would like each kind of context fact to be defined with its own key identifier in the schema itself. I will leave this as is for now, although I might consider this more in the future (if this approach isn't actually worth the overhead complexity) |
1 participant
... to provide better error-reporting when using general-purpose JSON Schema validators.