[Feature] Add Firebase Remote Config localization - #83
Merged
Conversation
Velord
force-pushed
the
feature/firebase-remote-localization
branch
7 times, most recently
from
August 19, 2026 17:29
fdacd89 to
0c1854f
Compare
Velord
force-pushed
the
feature/firebase-remote-localization
branch
9 times, most recently
from
August 20, 2026 10:05
dcc4225 to
4ae8998
Compare
Velord
force-pushed
the
feature/firebase-remote-localization
branch
from
August 20, 2026 10:34
4ae8998 to
5a5478c
Compare
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
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
Res.stringusage with theAppStringAPI backed by bundledcore/core-resource/src/commonMain/composeResources/files/localization.jsonlocalization.jsonas the bundled localization document and generates only type-safeAppString.xxxkeys; no generated default translation roster is maintainedLanguagePreferenceenum values (default,en,es) and keeps the resolved active language separate inLocalizationStatelanguageRosterconsistently in the localization schema and typedLocalizationStringMapvalues in the model:data:localization, with orchestration inLocalizationGatewaycommonMain; platform code is limited to locale/Firebase initialization where requiredInitializeLocalizationUC; initialization publishes the available document and performs the startup Remote Config refreshComposeScreenExample QAstrings.xmlresources separate; this PR does not generate Androidstrings.xmlfrom the localization JSON:app:android:processDevelopDebugMainManifestand verifies Develop/QA/Stage/Production compilation plus Konsist/detektFirebaseKit Android namespace
Firebase-KMP-Kit 0.4.0 publishes its Android library modules with the shared
com.firebasekitnamespace. The project disables AGP unique-package-name validation for this dependency while retaining Firebase-KMP-Kit as the KMP Remote Config implementation. CI runs Android manifest processing to catch regressions in this integration.Validation
Final validation is running on the current single-commit PR head. The workflow checks localization schema/publishing validation, QA reuse of the Develop Firebase client, localization/Desktop tests, Android manifest processing, all application environments, Konsist, and detekt.
The PR is maintained as exactly one commit.