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
running node ./scripts/i18n_extract.js --output-dir ./translations for workspace plugin, there will have few errors complaining i18n translation id need under workspace namespace.
ERROR I18N ERROR Error in src/plugins/workspace/common/constants.ts
Error: Expected "core.ui.getStarted.label" id to have "workspace" namespace. See .i18nrc.json for the list of supported namespace
To Reproduce
Steps to reproduce the behavior:
Add "workspace": "src/plugins/workspace" to .i18nrc.json
Run node ./scripts/i18n_extract.js --output-dir ./translations
Expected behavior
no error when extract i18n resources
OpenSearch Version
main
Dashboards Version
main, 2.x
Plugins
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):
OS: [e.g. iOS]
Browser and version [e.g. 22]
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
@Hailong-am Hi, I have read Developer Guide of i18n translation , follow the document the plugin only working with local code (it work when yarn start the project) now I want to apply i18n translation for Docker, it is impossible? Thank you
Describe the bug
running
node ./scripts/i18n_extract.js --output-dir ./translations
for workspace plugin, there will have few errors complaining i18n translation id need underworkspace
namespace.To Reproduce
Steps to reproduce the behavior:
"workspace": "src/plugins/workspace"
to.i18nrc.json
node ./scripts/i18n_extract.js --output-dir ./translations
Expected behavior
no error when extract i18n resources
OpenSearch Version
main
Dashboards Version
main, 2.x
Plugins
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: