Open epenet opened 5 days ago
These are all open ones (without a pending PR)
...
Edit: converted to task list in the description
These are all open ones (without a pending PR)
Thanks, I've converted to a task list in the description
we have some integrations (eq. generic
and webmin
, properly much more) which redirects possible connection errors direct into the errors
dict to the async_show_form
, those they can have unexpected or unforeseen error values, which can't be translated :thinking: Should we adjust the tests in this case, so they test only expected errors? Or do we've the possibility to work with placeholders also for errors in flow forms?
we have some integrations (eq.
generic
andwebmin
, properly much more) which redirects possible connection errors direct into theerrors
dict to theasync_show_form
, those they can have unexpected or unforeseen error values, which can't be translated 🤔 Should we adjust the tests in this case, so they test only expected errors? Or do we've the possibility to work with placeholders also for errors in flow forms?
Might be worth confirming with a core member... I think we normally use "unknown" and log the full details
I think we normally use "unknown" and log the full details
Like that yes, we can only translate known errors e.g. there is no placeholders or such.
The problem
As a developper, it's very easy to forget adding all expected translation keys into
strings.json
I am working on catching this within the regular test routines (see https://github.com/home-assistant/core/pull/127787)If you would like to help, take a look at the resulting failures and see if you can add/fix: https://github.com/home-assistant/core/pull/127787/checks