[studio][i18n] Extend translation keys & add useLanguage compatible alias in LangContext#433
Open
zhaohai666 wants to merge 3 commits into
Open
Conversation
…omprehensive translation keys - Add useLanguage as compatibility alias for useLang in LangContext.tsx - Add 400+ translation keys to translations.ts covering: - Login, Ops, Topic, Group/Consumer, Message, DLQ, Message Trace - Broker detail, Proxy cluster, SSL settings, Namespace - Alert management, LiteTopic, Producer - Extended common keys - All keys follow dot-notation convention (e.g., topic.name, group.count) - Keys mapped from frontend-new uppercase underscore format to dot-namespace format
zhaohai666
force-pushed
the
feature/studio-i18n-language-context
branch
from
July 16, 2026 06:36
2c4b553 to
ade82a1
Compare
- Remove duplicate 'common.export' and 'common.searchPlaceholder' keys in translations.ts - Use defineConfig from vitest/config instead of vite for test property types - Add vitest/globals type reference in test/setup.ts for beforeEach
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR enriches i18n translation resources and provides a compatible language hook alias to facilitate component migration from
frontend-newto the new web frontend.Branch: feature/studio-i18n-language-context
Commit: 8b49561, 2 files changed, +426 lines
Close #【Related Issue】
Changes
1.
LangContext.tsxuseLanguageas a compatible alias of existinguseLanghookfrontend-newwhich referenceuseLanguagewithout modification2.
translations.tsExpand translation entries from 344 lines to 763 lines, adding 400+ new translation keys covering multiple business modules.
All keys adopt dot-separated namespace specification and are migrated from the uppercase underscore format used in
frontend-new:login.*: Login page (11 keys)ops.*: Operations page (4 keys)topic.*: Topic management (30 keys)group.*: Consumer group management (40 keys)message.*: Message query (25 keys)dlq.*: Dead letter queue (3 keys)trace.*: Message trace (5 keys)broker.*: Broker details (25 keys)proxy.*: Proxy cluster management (20 keys)ssl.*: SSL configuration (30 keys)ns.*: Namespace management (30 keys)alert.*: Alert management (30 keys)liteTopic.*: LiteTopic management (35 keys)producer.*: Producer related (2 keys)common.*: Extended general common labels (40+ keys)Purpose
frontend-newuseLanguagecompatibility aliasVerification
useLanganduseLanguagework normally