Skip to content
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

Fix exit codes and max-warnings on quiet #578

Merged
merged 4 commits into from
May 11, 2024
Merged

Conversation

dbale-altoros
Copy link
Collaborator

This is a breaking change in terms that the program changed how the exit codes are implemented

Solhint will exit with 0
when execution was ok and there were no errors when evaluating the code according to the rules

Solhint will exit with 1
when execution was ok and there are errors reported
when execution was ok and max warnings is lower than the reported warnings

Solhint will exit with 255
when there's an error in the execution (bad config, writing not allowed, wrong parameter, file not found, etc)

QUIET mode (-c quiet) option now works with the warnings and may exit with 1 if there are more than defined by user

@dbale-altoros dbale-altoros force-pushed the fix-exit-codes branch 6 times, most recently from 25c2ad2 to 1e65c0d Compare May 11, 2024 22:19
@dbale-altoros dbale-altoros merged commit 4de35dc into develop May 11, 2024
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant