Closed Susccy closed 1 year ago
A minimal reproduction is needed
The behavior can be easily deduced from the source code:
The unnecessary error is logged in line 111. As you can see it will still try more languages after the error is logged, meaning it is expected behavior when utilizing fallback languages and thus not an error. Here it should be a warning at most.
Only if the translation couldn't be found in any fallback language, then it should throw an error.
@Susccy I agree that the log on line 111 should not be presented since it's indeed expected behaviour. Would you be able to create a PR that removes this log, but still gives a log when the translation couldn't be found in any fallback language?
I will look into it when I have time.
Why is this error constantly thrown in the console despite the translations working fine with fallback languages? If a fallback language is provided, this shouldn't be an error because it is expected and wanted behavior. It should be a warning at most but even then I'd want to be able to disable the log completely as it is totally unnecessary.