Allow to translate empty strings

[VincentLanglet]

Hi @JanEbbing

Currently an exception is thrown when we try to translate an empty string.
This seems to be an unnecessary check because if I remove the check manually in my vendors, the API works fine.

When receiving multiple users inputs and if we want to translate for instance

['foo', 'bar', '', 'baz']

This seems unnecessary to ask us to

• Filter the '' value
• Translate [0 => 'foo', 1 => 'bar', 3 => 'baz'] (while the API call lose the initial keys)
• Receving the translation [0 => 'Tfoo', 1 => 'Tbar', 2 => 'Tbaz']
• Insert back the empty string in the right position to get [0 => 'Tfoo', 1 => 'Tbar', 2 => '', 3 => 'Tbaz']

While an API call with ['foo', 'bar', '', 'baz'] seems to works fine if the input validation is removed.

[JanEbbing]

Thanks for this! I agree the behaviour is inconsistent, e.g. in deepl-python translating '' raises an error but translating [''] works fine. I'm checking internally why we don't allow empty string and how we want to handle this, let me get back to you.

[JanEbbing]

Agreed that we should allow translating empty string. I'll merge this

[JanEbbing]

Nit: For the future, we use conventional commits, so commit messages should start with something like fix:, docs:, feat: etc
Also we keep a CHANGELOG.md file (I'm looking to automate that in the future based on commit messages, as we have the classification already)