feat: localize Help page strings into react-i18next - #22
Merged
Conversation
## Closes stellar-kracken#5 ### What does this PR do? Moves all hardcoded user-facing strings from Help.tsx into the react-i18next translation system under a new help namespace. ### Changes: Help.tsx - Added useTranslation hook. Replaced 23 hardcoded English strings with t() calls using namespaced keys (help.title, help.intro, help.categories, etc). en.json through ar.json - Added help namespace with 23 translated keys in all 8 supported languages. ### How was this tested? Manual review confirms no hardcoded strings remain. All keys follow existing naming conventions. Page renders identically. ### Checklist: [x] Code conforms to style guidelines [x] No hardcoded user-facing strings remain [x] Key names consistent with existing convention [x] Translations added for all 8 supported languages
4 tasks
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
2 participants
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.
Closes #5
What does this PR do?
Moves all hardcoded user-facing strings from Help.tsx into the react-i18next translation system under a new help namespace.
Changes: Help.tsx
How was this tested? Manual review confirms no hardcoded strings remain. All keys follow existing naming conventions. Page renders identically.
Checklist:
[x] Code conforms to style guidelines
[x] No hardcoded user-facing strings remain
[x] Key names consistent with existing convention
[x] Translations added for all 8 supported languages