-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrect rules are skipped without mention, giving the impression all is well #218
Comments
Apparently I have the same behaviour with several other operators (not-empty, present, in) that return OKAY when there are purposefully created bugs that should fail the check. Using Would it be possible to change this behaviour into a hard fail? I think it's much safer to bail out when a rule is incorrect rather than skipping it without mention which implies all is well, like when the check succeeds. |
Hey :) Thanks for writing this utility.
I have some questions regarding missing keys or checks that are suppose to fail but dont.
I have the following yaml:
When I on purpose remove a few chars so that the assertion is supposed to fail:
.... The check still succeeds.
Is this intended behaviour? It looks like a regex is used or a string in string comparison where the full key should be checked instead.
The text was updated successfully, but these errors were encountered: