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
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."
The text was updated successfully, but these errors were encountered:
馃殌 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."
The text was updated successfully, but these errors were encountered: