validate.py: Make missing schemas a fatal error #270
Merged
Conversation
This file contains 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
It doesn't make sense that missing schemas, e.g. caused by typos in the event version in the examples, only result in warnings and a zero exit code. Change this so that a missing schema is as bad as a failed validation.
t-persson
approved these changes
Sep 15, 2021
m-linner-ericsson
approved these changes
Sep 15, 2021
e-backmark-ericsson
approved these changes
Sep 16, 2021
e-backmark-ericsson
pushed a commit
to e-backmark-ericsson/eiffel
that referenced
this pull request
Apr 13, 2022
It doesn't make sense that missing schemas, e.g. caused by typos in the event version in the examples, only result in warnings and a zero exit code. Change this so that a missing schema is as bad as a failed validation.
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.
Applicable Issues
Fixes #268
Description of the Change
It doesn't make sense that missing schemas, e.g. caused by typos in the event version in the examples, only result in warnings and a zero exit code. Change this so that a missing schema is as bad as a failed validation.
Alternate Designs
None.
Benefits
Decreased risk of mistakes going unnoticed.
Possible Drawbacks
None? I suppose we'd break any use case where missing schema files are normal, but I don't know what that use case would be.
Sign-off
Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and have the right to submit it under the open source license indicated in the file; or
(b) The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or
(c) The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it.
(d) I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.
Signed-off-by: Magnus Bäck <magnus.back@axis.com>