Hi everyone! đź‘‹
I need a quick clarification regarding the LANGUAGE field in the advanced UI settings.
Currently, the input field only accepts numeric values, but when sending the task, the backend throws a validation error expecting 2-letter ISO language codes (e.g., it, en, es).
Here is the log output:
Plaintext
Invalid Language code '2'. Available codes: ar, az, bg, bn, ca, cs, da, de, el, en, es, fa, fi, fr, he, hi, hr, ht, hu, id, is, it...
[SKIP] Task 1 failed validation
Is this a known bug in the frontend form validation, or is there a specific index mapping/number we should use? Leaving it empty works, but it would be great to know if the text field can be updated to accept ISO strings directly.
Thanks!
Hi everyone! đź‘‹
I need a quick clarification regarding the LANGUAGE field in the advanced UI settings.
Currently, the input field only accepts numeric values, but when sending the task, the backend throws a validation error expecting 2-letter ISO language codes (e.g., it, en, es).
Here is the log output:
Plaintext
Invalid Language code '2'. Available codes: ar, az, bg, bn, ca, cs, da, de, el, en, es, fa, fi, fr, he, hi, hr, ht, hu, id, is, it...
[SKIP] Task 1 failed validation
Is this a known bug in the frontend form validation, or is there a specific index mapping/number we should use? Leaving it empty works, but it would be great to know if the text field can be updated to accept ISO strings directly.
Thanks!