Require type for oneOf mutual exclusion #5426
Merged
+42
−9
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello!
The following config:
is considered broken under current JSON schema for config:
for two reasons:
oneOf
requires exactly one of each options. When both sub-schemas match the object, the validation fails."required"
.The given YAML:
type
property, it should be one among["module"]
.". Since it doesn't have that property, the statement is (vacuously) true."path"
property.". It does.I think the
oneOf
clause was there to do a mutual exclusion between "module" and "goplugin" type. Since the default is considered the latter, the "module" case should explicitly require for the property to be present.This PR adds the requirement, and adds some test cases for that.
Since I'm new to the code base, I don't know which files among
jsonschema/*.json
needs to change; please point me if I'm wrong.