fix(i18n): disambiguate paid feature availability keys#2134
Conversation
Rename the ambiguous i18n key to feature available in paid version and add a dedicated feature not available key in all locale files. This avoids confusion while using i18n keys by separating generic unavailability from paid-only messaging.
Greptile SummaryThis PR disambiguates two previously conflated i18n keys across all 31 locale files: the old
Confidence Score: 5/5Safe to merge — purely additive i18n changes with no logic alterations; existing callsites get a more accurate generic message. The change is limited to locale JSON files and the TypeScript type definition. Existing runtime behavior in terminalSettings.js is actually improved (correct generic message instead of a misleading paid-version message). The new key is unused but harmless. No files require special attention; all 31 locale files follow the same consistent pattern. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A["strings lookup in JS code"] --> B{"Which key?"}
B -->|"feature not available"| C["Generic: 'This feature is not available.'"]
B -->|"feature available in paid version"| D["Paid: 'This feature is only available in paid version.'"]
E["terminalSettings.js L242 / L246"] --> B
F["(no callsite yet)"] -.->|future use| D
C --> G["alert shown to user"]
D -.-> H["(never shown — key unused)"]
Reviews (2): Last reviewed commit: "update: lang TS declaration file" | Re-trigger Greptile |
|
@greptileai review again. |
b60058a
into
Acode-Foundation:main
Summary
Why
This change avoids confusion while using i18n keys by clearly separating generic feature unavailability from paid-only availability messaging.
Notes