Use anyOf over oneOf when comparing JSON schema of .laminas-ci.schema.json
#68
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
With v1.11.0, the JSON schema validation for
.laminas-ci.jsonwas added.Since that schema uses
oneOf, it actually must not match more than one schema. The idea behind this was to ensure thatadditional_checkscannot be used withchecks. That worked well when eitherchecksoradditional_checkswere present in the.laminas-ci.jsonfile. But if neither of these are present, the schema validation fails.Therefore, we have to use
anyOfwhich ensures that at least one of the schemas matches.