You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice if the validator returned a non-zero exit code when used on the cli with the --input option, either optionally behind a cli flag (e.g. --exit-code) or simply by default if --input is used. Perhaps it would even be possible to use different exit codes depending on severity of warnings or errors found (e.g. code 1 for fatal errors, 2 if there were no fatal errors but some warnings, etc.).
My motivation for this is that it'd make it much easier to use the tool in scripts or CI pipelines; currently the easiest way to answer "did validation fail?" i can find is to parse the json output with jq and check the validations (or issues_count) keys directly.
The text was updated successfully, but these errors were encountered:
hm, that would of course also be an option — though it'd also make it harder to have a three-way split in e.g. a shell script (e.g. "do $x when everything's fine, $y if there were warnings, $z if there were errors).
but really i don't have a strong opinion either way, I can work with both :)
It would be nice if the validator returned a non-zero exit code when used on the cli with the
--input
option, either optionally behind a cli flag (e.g.--exit-code
) or simply by default if--input
is used. Perhaps it would even be possible to use different exit codes depending on severity of warnings or errors found (e.g. code1
for fatal errors,2
if there were no fatal errors but some warnings, etc.).My motivation for this is that it'd make it much easier to use the tool in scripts or CI pipelines; currently the easiest way to answer "did validation fail?" i can find is to parse the json output with
jq
and check thevalidations
(orissues_count
) keys directly.The text was updated successfully, but these errors were encountered: