Exit with failure code with faults were found #33
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.
Fault is a CLI tool run by developers to check their work. Therefore it's reasonable to assume it will someday be used in CI builds. In that situation, a user would expect the default behavior to return non-zero exit code failing the pipeline.
If I've understood the various modes of execution correctly, this change will cause
fault
to return 1 when faults were found.Alternatives
Other conventions worth considering: allow an option to disable the meaningful return code (e.g.
--quiet
), or default to returning 0 and provide--exit-code
option likegit-diff
does.I opted for what seemed like the best default and avoiding customization unless it proved necessary, open to other ways.