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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

fail-on-errors #618

Open
christian1koch opened this issue Jul 21, 2022 · 0 comments
Open

fail-on-errors #618

christian1koch opened this issue Jul 21, 2022 · 0 comments

Comments

@christian1koch
Copy link

christian1koch commented Jul 21, 2022

馃殌 Feature Proposal

The idea of this feature is for the parser to fail with exit code 1, in the same way that fail-on-warnings and fail-on-update works.

Motivation

The reason for me to propose this option, is that there are times where the parser would find and error, but instead of not writing anything at the end, it overrides the translation files, resetting all the translations to default, which can be troublesome since then you would have to bring the translation files to an older state or add all the translations manually again.

Example

At the end, a message would appear saying something like : " [error] Some errors were found and failOnErros was enabled. Exiting...
error Command failed with exit code 1."

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

No branches or pull requests

1 participant