You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When starting superset using docker-compose-non-dev.yml, many messages are rendered untranslated, though the .po files include translations for their keys.
How to reproduce the bug
Enable a rather complete language in superset_config_docker.py:
When starting superset using docker-compose-non-dev.yml, many messages are rendered untranslated, though the .po files include translations for their keys.
How to reproduce the bug
docker-compose -f docker-compose-non-dev.yml' p -d
Expected results
See messages translated in .po files to appear translated in the frontend
Actual results
Messages translated in .po files appear untranslated in the frontend
Checklist
Make sure to follow these steps before submitting your issue - thank you!
Additional context
The text was updated successfully, but these errors were encountered: