fix: exposed missing strings to translations#1168
Merged
spacecowboy merged 1 commit intoJun 16, 2026
Merged
Conversation
Owner
|
Thanks @himu-gupta ! |
spacecowboy
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.
What does this change?
Fixes #1162.
Moves two app-owned English messages into string resources so they can be picked up by translation tooling:
Checklist
./gradlew ktlintFormatand committed the resultMIGRATION_N_N+1inAppDatabase.kt(not applicable; no schema change)app/src/androidTest/.../db/room/(not applicable; no schema change)Verification:
./gradlew ktlintCheck compileFdroidDebugKotlingit diff --checkScreenshots (if UI change)
Not included. This change exposes existing text to translation resources without changing the UI layout.