Architecture
- Location:
src/i18n/ - Current language: English only (
en) - Structure: Feature-based translation files
- Framework: Vue I18n with Composition API (non-legacy mode)
Basic Usage
Using in Components
Adding New Translations
1. Add to Translation File
Find the appropriate file insrc/i18n/locales/en/ and add your translation:
2. Use in Component
Creating a New Feature Translation File
When adding a new feature, create a dedicated translation file:1. Create the Translation File
2. Register in Index
Key Naming Convention
Structure
globalSettings.errors.configNotSetmcpCatalog.filters.byCategorycommon.buttons.savevalidation.required
Rules
- Use camelCase for keys
- Group by feature (globalSettings, mcpCatalog, teams)
- Use descriptive names (avoid generic keys like ‘msg1’, ‘error1’)
- Common translations go in
common.ts - Validation messages can be shared or feature-specific
Parameters and Pluralization
Parameters
Pluralization
Quick Reference
Common Translation Keys
| Category | Key Example | Location |
|---|---|---|
| Buttons | buttons.save, buttons.cancel | common.ts |
| Validation | validation.required, validation.email | common.ts |
| Status | common.status.running | common.ts |
| Errors | {feature}.errors.{errorType} | Feature file |
| Success | {feature}.messages.success | Feature file |
| Forms | {feature}.form.{field}.label | Feature file |

