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

exit with a different code when the linter is configured incorrectly #134

Merged
merged 9 commits into from
Feb 4, 2024

Conversation

juanpcapurro
Copy link
Contributor

@juanpcapurro juanpcapurro commented Jan 29, 2024

vs when errors are found in linted files

also, exit eagerly instead of just printing to stderr and chugging along, since that'd prompt the programmer to realize of their mistake sooner

merge after #132
closes #80

@juanpcapurro juanpcapurro marked this pull request as ready for review January 29, 2024 23:57
@juanpcapurro
Copy link
Contributor Author

@99effy you started implementing something similar a few weeks ago iirc, do you have any input?

@juanpcapurro juanpcapurro changed the title exit with a different exit code when the linter is configured incorrectly exit with a different code when the linter is configured incorrectly Jan 30, 2024
@juanpcapurro juanpcapurro merged commit eb741aa into master Feb 4, 2024
9 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.

exit early with a different error when --ignore-path points to a non-existing or invalid file
1 participant