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
{{ message }}
Repository navigation
[Playground] Is upstream open to i18n support for Cube Playground? #11992
We use Cube as the semantic layer in an internal analytics platform, and our
team members work primarily in Chinese. The Playground (dev console at :4000)
is the main interface our non-English-speaking developers and analysts interact
with when building data models and debugging queries.
Before writing any code, we'd like to ask: would the maintainers be open to
adding i18n support to the Playground?
Concretely, we'd envision:
Introducing a lightweight i18n layer (e.g. react-i18next) in
packages/cubejs-playground
Extracting hardcoded UI strings into locale files (en, zh-CN to start)
A language toggle persisted in localStorage, defaulting to English —
zero behavior change for existing users
We understand the Playground is a dev tool and English-only is fine for most
users, so we don't want to invest in a large PR that has no chance of being
merged. If upstream is open to it, we're happy to do the extraction work and
maintain the zh-CN locale long-term. If not, we'll keep a local fork/patch.
Activity