feat(i18n): add complete English and Chinese localization - #4
Merged
Conversation
Introduce limited i18n with English, zh-CN and zh-TW via i18next + react-i18next. Language persists in SQLite settings and can be switched in the Settings screen. Core screens (tabs, today, pantry, rescue, insights, settings, onboarding) now use translation keys. Jest setup with global react-i18next mock using English translations.
DrEden33773
changed the title
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.
Summary
Completes T23 with supported
en,zh-CN, andzh-TWapplication/content localization while preserving canonical English domain fields and all user/OFF free text.zhto Traditional ChineseLocal verification
npm run typecheck— PASSnpm run lint— PASS, 0 errors and 1 pre-existing development-only warningnpm test -- --runInBand— PASS, 58 suites / 162 testsnpm run export:android— PASSnpm run export:ios— PASS (export only; no iOS device claim):app:lintVitalRelease— PASSCI boundary
Pull requests run the fast deterministic gates: typecheck, lint, 58 Jest suites / 162 tests, Android/iOS exports, and Windows/WSL contracts. Main pushes and manual runs additionally build and publish a cached x86_64 release APK.
Run 30092316784 completed the release APK build, then the hosted emulator disappeared (
emulator-5554 not found) and the runner kept polling ADB. That run was cancelled instead of waiting for a known-bad surface to time out. The three Maestro journeys remain available throughworkflow_dispatch; they are supporting hosted-emulator evidence rather than a per-commit gate. Final Android surface acceptance remains in F1-F4, and no local Android-device or iOS-device claim is made here.Evidence:
qa/evidence/T23-i18n/