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
Describe the bug
core.localization.localization in cloudbeaver.conf and .cloudbeaver.runtime.conf does not work
To Reproduce
I have set the CLOUDBEAVER_CORE_LOCALIZATION environment variable to zh, but the interface still displays in the default English. When I add "core.localization.language" to the configuration file and set it to zh, the language configuration takes effect. I suspect that there is a mistake in the configuration item name in cloudbeaver.conf. It should be core.localization.language instead of "core.localization.localization", because the source code reads the configuration "core.localization.language".
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
OS: windows 11
Browser edge
Version 25
Additional context
Add any other context about the problem here, e.g. error log.
The text was updated successfully, but these errors were encountered:
Describe the bug
core.localization.localization in cloudbeaver.conf and .cloudbeaver.runtime.conf does not work
To Reproduce
I have set the CLOUDBEAVER_CORE_LOCALIZATION environment variable to zh, but the interface still displays in the default English. When I add "core.localization.language" to the configuration file and set it to zh, the language configuration takes effect. I suspect that there is a mistake in the configuration item name in cloudbeaver.conf. It should be core.localization.language instead of "core.localization.localization", because the source code reads the configuration "core.localization.language".
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here, e.g. error log.
The text was updated successfully, but these errors were encountered: