Return non-zero exit code on failure to extract strings

[djbb7]

🚀 Feature Proposal

Motivation

The scanner sometimes fails to extract strings due to the selected keys. However, the command exit code is always 0.
We run the local extraction on a pre-commit hook, and this type of human errors are common. It would be very useful if the i18next-scanner could return non-zero exit code in this case.

Example

// The first case creates a string in the locale json file 
{t('key1, 'Foo')}

// The second case tries to create an object in the `nested1` key,
// but it fails since there is already a literal in that key
{t('key1.title', 'Bar')}

The exit code of the i18next-scanner in this case is 0 and the output is:

i18next-scanner: failed to process file Example.tsx
i18next-scanner: count=1, file="Example.tsx"
✨  Done in 6.30s.

[gex]

i was looking for the same, it's a bummer it's not implemented yet. my other idea was to use a --dry-run option or something like that to list the possible changes without actually making them but unfortunately the output is always empty even if there was a change.

i added a little script to my pre-commit hook to check the git status of the locale files and in case they're changed but not staged i exit with an error from the hook. i guess this could be further improved with combining this with lint-staged but right now this is enough for us.