Conversation
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Note
Due to the large number of review comments, Critical severity comments were prioritized as inline comments.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (5)
src/config/locales/ca-ES.json (1)
1-1433:⚠️ Potential issue | 🟠 MajorPlease keep translation-key source changes in
en-US.jsononly.This PR modifies
src/config/locales/ca-ES.jsondirectly. Per repo workflow, key additions/updates should be made insrc/config/locales/en-US.json, with other locales synchronized by Crowdin automation.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration and should not be manually edited in pull requests.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/ca-ES.json` around lines 1 - 1433, This PR incorrectly modifies the Catalan locale file (ca-ES.json) instead of updating the source English keys; revert any changes made to ca-ES.json and apply the same key additions/updates to the canonical locale file (en-US.json) instead (e.g., ensure keys like "posting_authority", "auth_upgrade", and any newly added strings are present/updated in en-US.json); leave ca-ES.json untouched so Crowdin can synchronize translations automatically and remove your manual edits from the PR.src/config/locales/got-DE.json (1)
1-1433:⚠️ Potential issue | 🟠 MajorPlease remove manual changes from
got-DE.json.This file should be updated by Crowdin sync, not by direct PR edits.
Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/got-DE.json` around lines 1 - 1433, The got-DE.json locale file contains manual edits (e.g., keys like "profile.havent_commented", "post_poll.choice_placeholder", "editor.reward_decline", etc.) that must be removed — revert this file to the Crowdin-synced version (undo any changes in got-DE.json) and remove it from the PR; only modify en-US.json for adding/updating translation keys and let Crowdin propagate changes to other locale files. Ensure the PR only includes changes to en-US.json and, if needed, add a short commit message like "Revert manual changes to got-DE.json — use Crowdin sync" so future merges don't reintroduce manual locale edits.src/config/locales/ku-TR.json (1)
1-1433:⚠️ Potential issue | 🟠 MajorDo not manually edit non-
en-USlocale files in this repo.This file should be Crowdin-synced, so these manual additions should be reverted from the PR and kept only in
src/config/locales/en-US.json.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/ku-TR.json` around lines 1 - 1433, The PR has manual edits to a non-en-US locale file (ku-TR.json) which must not be edited directly; revert all manual changes in src/config/locales/ku-TR.json back to the Crowdin-synced state, remove any added or modified keys you introduced, and instead make your translation/key additions only in src/config/locales/en-US.json (e.g., add/update the new keys under the top-level objects like "profile", "editor", or "settings" you intended to change) so Crowdin can propagate them; ensure the PR contains only the en-US.json changes and a revert/restore of ku-TR.json before re-requesting review.src/config/locales/de-DE.json (1)
1-1433:⚠️ Potential issue | 🟠 Major
de-DE.jsonupdates should be excluded from manual PR changes.These additions should come from Crowdin sync; keep source key updates in
src/config/locales/en-US.jsononly.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/de-DE.json` around lines 1 - 1433, The PR contains manual updates to the German locale file (src/config/locales/de-DE.json — e.g. keys under "profile", "post_poll", "editor", etc.) which must not be edited directly; revert de-DE.json to its previous committed state (remove all new/changed translations from this file) and ensure only src/config/locales/en-US.json carries the source key changes; update the commit/PR message to state that locale syncs are managed by Crowdin and that translation files must come from the Crowdin sync pipeline.src/config/locales/fr-FR.json (1)
1-1433:⚠️ Potential issue | 🟠 MajorThis locale file should not be edited directly.
Please remove direct
fr-FR.jsonedits from this PR and keep key changes inen-US.jsononly so Crowdin can propagate translations.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/fr-FR.json` around lines 1 - 1433, The PR includes direct edits to src/config/locales/fr-FR.json which must not be modified directly; revert or remove any changes made to the "fr-FR.json" file (e.g., the added/edited translation keys such as entries under "profile", "editor", "wallet", etc.) and instead apply your key additions/updates to the canonical locale file en-US.json so Crowdin can propagate translations; ensure the PR only contains the en-US.json changes and no modifications to other locale JSON files before re-submitting.
🟠 Major comments (37)
src/config/locales/fil-PH.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorRemove manual edits from
fil-PH.json; update onlyen-US.jsonin PRs.These additions should not be committed in non-
en-USlocale files in this repo workflow. Please move key changes tosrc/config/locales/en-US.jsononly and let Crowdin sync localized files automatically.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are synchronized via Crowdin and should not be manually edited in pull requests.
Also applies to: 683-688, 1402-1405, 1419-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/fil-PH.json` around lines 612 - 621, The fil-PH locale was manually edited — revert any added/changed keys (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed" and the other key groups you modified at the other ranges) back to the Crowdin-synced state and instead add/update those keys only in the en-US locale (src/config/locales/en-US.json) so Crowdin can propagate translations; locate the changed keys in the fil-PH JSON (use the key names above to find them), remove your manual edits or restore the original file, and place all new/updated keys into en-US.json before committing.src/config/locales/sa-IN.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorRevert manual edits in non-
en-USlocale file.These additions in
src/config/locales/sa-IN.jsonshould not be manually committed. Per repository workflow, onlysrc/config/locales/en-US.jsonshould be changed in PRs, and other locale files are synced via Crowdin. Please remove these direct edits from this file and keep source-string updates inen-USonly.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration and should not be manually edited in pull requests.
Also applies to: 683-688, 1402-1405, 1419-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/sa-IN.json` around lines 612 - 621, This file contains manual edits to a non-source locale (sa-IN) that must be reverted; remove the added/modified keys (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed" and the other ranges referenced) so that src/config/locales/sa-IN.json matches the last committed Crowdin-synced version, and instead make any intended source-string changes only in src/config/locales/en-US.json; ensure no other manual changes remain in sa-IN.json before committing.src/config/locales/el-GR.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorPlease avoid direct edits to
src/config/locales/el-GR.jsonin this PR.These additions should be made in
src/config/locales/en-US.jsononly, then propagated via Crowdin sync. Keeping manual edits in non-en-USlocale files risks diverging from the repo’s localization flow.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files (e.g., es-ES.json, de-DE.json, etc.) are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.
Also applies to: 683-688, 1402-1405, 1419-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/el-GR.json` around lines 612 - 621, The change mistakenly adds translation keys directly to el-GR.json (keys like "operation_failed_with_reason", "wallet_refresh_failed", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed" referenced in the diff); revert these manual edits from src/config/locales/el-GR.json and instead add the new/updated keys to src/config/locales/en-US.json only, then let the Crowdin sync propagate them to other locale files (also remove any other manual edits noted at the other ranges like 683-688, 1402-1405, 1419-1431).src/config/locales/pt-PT.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorPlease avoid direct edits to
pt-PT.jsonin this repo workflow.These additions should be introduced in
src/config/locales/en-US.jsononly, then synced to other locales via Crowdin automation. Please move/revert these non-en-USlocale edits in this PR.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; other locale files are auto-synced via Crowdin integration.
Also applies to: 683-688, 1402-1405, 1420-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/pt-PT.json` around lines 612 - 621, Revert the direct edits to src/config/locales/pt-PT.json for the translation keys added/changed (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed" and the other mentioned ranges) and instead add these new/updated keys only to src/config/locales/en-US.json; after adding them to en-US.json, remove the changes from pt-PT.json so Crowdin can propagate translations automatically. Ensure you update only en-US.json and leave other locale files untouched in this PR.src/config/locales/ur-IN.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorAvoid manual edits in non-
en-USlocale files.Line 612 onward introduces new translation keys directly in
src/config/locales/ur-IN.json. In this repo, these non-en-USlocale files are Crowdin-synced, so manual edits here should be removed and key additions should be made insrc/config/locales/en-US.jsononly.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration.
Also applies to: 683-688, 1402-1405, 1419-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/ur-IN.json` around lines 612 - 621, Remove the manual additions from the Crowdin-synced non-en-US locale file (src/config/locales/ur-IN.json): delete the newly added keys such as "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed" (and the other manual edits at the ranges mentioned) and instead add these keys only to src/config/locales/en-US.json so Crowdin can sync translations for other locales; ensure you only modify en-US.json for new/updated translation keys and revert any non-en-US locale changes before committing.src/config/locales/vi-VN.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorDo not directly modify non-
en-USlocale files in this repoThese additions in
src/config/locales/vi-VN.jsonshould not be committed directly. Please move key-definition updates toen-US.jsononly and let Crowdin synchronization propagate them tovi-VN.jsonautomatically.Based on learnings: In this repository, only
en-US.jsonshould be manually edited for translation key updates; other locale files are synced via Crowdin.Also applies to: 683-688, 1402-1405, 1419-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/vi-VN.json` around lines 612 - 621, The vi-VN.json contains new translation key definitions (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed") that must not be edited directly; revert these changes in vi-VN.json and instead add the new keys and English strings to en-US.json (maintain identical key names), then commit only en-US.json so Crowdin can propagate translations to vi-VN.json automatically.src/config/locales/it-IT.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorDo not manually edit non-
en-USlocale files in this repo.These additions are in
src/config/locales/it-IT.json, but this repository’s localization flow expects manual key updates only insrc/config/locales/en-US.json, with other locales synced by Crowdin. Please move these key changes toen-US.jsonand let Crowdin propagate them.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration.
Also applies to: 683-688, 1402-1405, 1419-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/it-IT.json` around lines 612 - 621, The new translation keys (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed" and the other ranges noted) were added directly to it-IT.json; move these additions into the canonical locale file en-US.json instead, then remove them from it-IT.json (and any other non-en-US locale files listed) so only en-US.json contains the new keys and Crowdin can propagate translations; ensure you add the keys with their English text to the en-US.json entries (using the same key names above) and revert the changes in the localized files before committing.src/config/locales/hy-AM.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorPlease avoid manual edits in
hy-AM.json; keep localization key changes inen-US.jsononly.These additions should come from Crowdin sync for non-
en-USlocales. Please move the key additions tosrc/config/locales/en-US.jsonand drop direct edits in this file to prevent sync conflicts/overwrites.Based on learnings: In the ecency-mobile repository, only the
en-US.jsonlocale file should be modified when adding/updating translation keys; other locale files are automatically synchronized via Crowdin integration.Also applies to: 683-688, 1402-1405, 1419-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/hy-AM.json` around lines 612 - 621, This file contains new translation keys added directly to hy-AM.json (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "boost_failed_with_reason", "add_withdraw_route_failed", etc.); move these newly added keys into src/config/locales/en-US.json instead and remove them from hy-AM.json so non-en-US locales remain CrowdIn-synced; update only en-US.json for new/changed keys and revert hy-AM.json to its previous state (drop the direct additions at the mentioned key ranges such as lines around the listed keys) to avoid sync conflicts.src/config/locales/sv-SE.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorAvoid direct edits to non-
en-US.jsonlocale files in PRs.These additions in
src/config/locales/sv-SE.jsonshould not be committed directly. Please keep source key updates insrc/config/locales/en-US.jsononly, then let Crowdin propagate them tosv-SE.json.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files (e.g., es-ES.json, de-DE.json, etc.) are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.
Also applies to: 683-688, 1402-1405, 1419-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/sv-SE.json` around lines 612 - 621, Revert the manual additions in src/config/locales/sv-SE.json (the newly added keys like "operation_failed_with_reason", "wallet_refresh_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed" and the other ranges noted) and instead add or update those translation keys only in src/config/locales/en-US.json so Crowdin can propagate them; ensure sv-SE.json contains no direct edits in this PR and keep all source-locale changes restricted to en-US.json.src/config/locales/lv-LV.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorDo not manually edit non-source locale files in this repo workflow.
These key additions were made directly in
src/config/locales/lv-LV.json. Per repo localization workflow, key additions/updates should be made insrc/config/locales/en-US.jsononly, and propagated to other locales via Crowdin sync.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration and should not be manually edited in pull requests.
Also applies to: 683-688, 1402-1405, 1419-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/lv-LV.json` around lines 612 - 621, This change added new translation keys directly into lv-LV.json (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed"); revert these manual edits in non-source locale files and instead add or update the keys only in the canonical en-US.json (so Crowdin can propagate them), then remove the duplicate/manual additions from lv-LV.json (and the other affected locale blocks noted) to comply with the localization workflow.src/config/locales/ms-MY.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorPlease avoid direct edits to non-
en-USlocale files in PRs.This PR updates
src/config/locales/ms-MY.jsondirectly (Lines 612-621, Line 683-Line 688, Line 1402-Line 1405, Line 1419-Line 1431), but the repo workflow indicates locale key updates should be made insrc/config/locales/en-US.jsononly, with other locales synced via Crowdin automation. Please remove manual non-en-USlocale edits from this PR and rely on sync output.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; other locale files are automatically synchronized via Crowdin integration.
Also applies to: 683-688, 1402-1405, 1419-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/ms-MY.json` around lines 612 - 621, This PR contains manual edits to non-en-US locale ms-MY.json for translation keys (e.g., operation_failed_with_reason, wallet_refresh_failed, wallet_refresh_missing_account, boost_failed, boost_failed_with_reason, add_withdraw_route_failed, remove_withdraw_route_failed, update_tokens_failed, swap_failed, market_data_load_failed); revert/remove those changes from src/config/locales/ms-MY.json in this PR and instead apply your key additions/updates only to src/config/locales/en-US.json so the Crowdin automation can propagate translations to other locales automatically.src/config/locales/hr-HR.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorPlease avoid direct edits in non-
en-US.jsonlocale files.This PR directly updates
src/config/locales/hr-HR.json. For key additions/updates, changes should be made insrc/config/locales/en-US.jsononly, then synchronized to other locales via Crowdin.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files (e.g., es-ES.json, de-DE.json, etc.) are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.
Also applies to: 683-688, 1402-1405, 1419-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/hr-HR.json` around lines 612 - 621, The changes were made directly in src/config/locales/hr-HR.json (e.g., keys like "operation_failed_with_reason", "wallet_refresh_failed", "boost_failed_with_reason", "add_withdraw_route_failed", etc. and other ranges noted at 683-688, 1402-1405, 1419-1431); revert those edits in hr-HR.json so it matches the repository’s synced locale state, then apply the intended key additions/updates to src/config/locales/en-US.json instead, commit that change, and trigger the Crowdin sync (or notify the localization team) so translations propagate to hr-HR and other locale files.src/config/locales/fi-FI.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorRemove manual edits from
fi-FI.jsonand keep localization key changes inen-US.jsononly.These additions should not be committed directly in a non-source locale file, since this repo’s localization flow syncs non-
en-USfiles via Crowdin. Please revert this file’s manual changes in this PR and keep source key updates insrc/config/locales/en-US.jsononly.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files (e.g., es-ES.json, de-DE.json, etc.) are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.
Also applies to: 683-688, 1402-1405, 1419-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/fi-FI.json` around lines 612 - 621, Revert the manual additions in src/config/locales/fi-FI.json (remove the newly added keys such as "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed" and the other ranges noted) so the non-source locale is unchanged; instead add or update these localization keys only in src/config/locales/en-US.json (the source locale) and leave fi-FI.json to be updated via Crowdin sync—ensure you revert the file to its previous committed state and confirm no other non-en-US locale files contain manual edits.src/config/locales/kk-KZ.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorDo not manually modify non-
en-USlocale files in PRs.This file includes direct translation key additions, but this repo’s localization workflow requires key additions/updates only in
src/config/locales/en-US.json; other locale files should be updated via Crowdin sync.Please move these additions to
en-US.json(or regenerate via Crowdin automation) and remove manual edits fromsrc/config/locales/kk-KZ.json.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.
Also applies to: 683-688, 1402-1405, 1419-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/kk-KZ.json` around lines 612 - 621, The keys added to src/config/locales/kk-KZ.json (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed" and the other ranges noted at 683-688, 1402-1405, 1419-1431) must not be manually edited in non-en-US locale files; remove these manual additions from kk-KZ.json and instead add or ensure the identical keys and English strings exist in src/config/locales/en-US.json (or trigger/regenerate via Crowdin automation) so the Crowdin sync can propagate translations to other locales. Ensure you only modify en-US.json for new/updated keys and leave all other locale files unchanged.src/config/locales/sq-AL.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorPlease avoid manual key updates in
sq-AL.json; updateen-US.jsononly.This PR adds new localization keys directly in a non-source locale file (
src/config/locales/sq-AL.json). Per project workflow, key additions/changes should be made insrc/config/locales/en-US.json, and other locales should be synced via Crowdin. Please move these key additions toen-US.json(or confirm this commit is purely Crowdin-generated sync output).Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; other locale files are auto-synchronized via Crowdin.
Also applies to: 683-688, 1402-1405, 1419-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/sq-AL.json` around lines 612 - 621, This change added new translation keys directly to src/config/locales/sq-AL.json (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed" and others in ranges noted 683-688, 1402-1405, 1419-1431); per project workflow, revert these additions in sq-AL.json and instead add or update the same keys in src/config/locales/en-US.json (or confirm the commit is the auto-generated Crowdin sync), then re-run the Crowdin sync process so other locales get updated rather than editing non-source locale files directly.src/config/locales/ka-GE.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorMove these key additions to
src/config/locales/en-US.jsononly.These updates are being made in
src/config/locales/ka-GE.json, but this repo’s localization workflow expects new/updated keys to be introduced only insrc/config/locales/en-US.jsonand then synchronized via Crowdin. Please revert direct edits in this file and apply the key additions inen-US.jsoninstead.Based on learnings, in the ecency-mobile repository only
en-US.jsonshould be manually modified, while other locale files are automatically synchronized via Crowdin integration.Also applies to: 683-688, 1402-1405, 1420-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/ka-GE.json` around lines 612 - 621, The new localization keys (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed" and the other key ranges noted) were added directly to src/config/locales/ka-GE.json but must be introduced only in src/config/locales/en-US.json per the repo workflow; revert the direct edits in ka-GE.json (remove these added keys) and instead add the exact key names and English strings to en-US.json so Crowdin can propagate them to other locales. Ensure you reference the same key names when adding them to en-US.json and do not manually modify other locale files.src/config/locales/bo-BT.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorThis Crowdin-managed locale file should not be edited directly.
Please revert these manual additions and apply locale-key source changes in
src/config/locales/en-US.jsoninstead.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration and should not be manually edited in pull requests.
Also applies to: 683-688, 1402-1405, 1419-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/bo-BT.json` around lines 612 - 621, This locale file (bo-BT.json) contains manual additions (e.g., keys like "operation_failed_with_reason", "wallet_refresh_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "market_data_load_failed" and others in the shown diff and also changes around lines noted by the reviewer) that must be removed; revert these edits from src/config/locales/bo-BT.json and instead add or update the corresponding keys in the source locale src/config/locales/en-US.json so Crowdin can propagate them; ensure you remove only the manual translations from bo-BT.json and commit the key changes to en-US.json (referencing the same key names above) so the Crowdin sync handles translations for other locales.src/config/locales/hu-HU.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorPlease keep this file unchanged in manual PR updates.
src/config/locales/hu-HU.jsonis expected to be synchronized via Crowdin, so direct additions here should be dropped from this PR.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration and should not be manually edited in pull requests.
Also applies to: 683-688, 1402-1405, 1419-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/hu-HU.json` around lines 612 - 621, The hu-HU locale file has manual edits that should not be included—revert the changes to the keys shown (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "market_data_load_failed" and the other ranges called out) so the file matches the Crowdin-synced source; instead make any translation key additions or updates in the en-US.json master locale only, then remove your manual modifications from this HU file so the PR contains no direct locale edits for Crowdin-managed languages.src/config/locales/da-DK.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorDo not manually modify non-
en-USlocale files in PRs.This file introduces direct locale-key edits in multiple sections, but repository workflow requires using
src/config/locales/en-US.jsonas the only manual source and letting Crowdin sync the rest. Please revert this file from the PR (or confirm this PR is the automated Crowdin sync output).Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration and should not be manually edited in pull requests.
Also applies to: 683-688, 1402-1405, 1419-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/da-DK.json` around lines 612 - 621, This PR modifies non-en-US locale file entries directly; revert the changes in src/config/locales/da-DK.json (the keys like "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed" and the other ranges mentioned) so the file matches the repository copy, and instead make any canonical key/value edits only in src/config/locales/en-US.json or confirm that this PR is the automated Crowdin sync output so no manual revert is required.src/config/locales/ro-RO.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorDirect changes to
ro-RO.jsonshould be reverted.For this repository, locale-key changes should be introduced only in
src/config/locales/en-US.json; translation files like this one are Crowdin-synced.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration and should not be manually edited in pull requests.
Also applies to: 683-688, 1402-1405, 1419-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/ro-RO.json` around lines 612 - 621, Revert the manual edits in ro-RO.json and remove the added/modified locale keys there; instead add or update these keys in the master en-US.json so Crowdin can propagate translations—specifically ensure the keys "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", and "market_data_load_failed" (and the other ranges called out: 683-688, 1402-1405, 1419-1431) are defined/updated only in en-US.json; do not commit any direct changes to locale files other than en-US.json.src/config/locales/uz-UZ.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorNon-
en-USlocale edits should be removed from this PR.These key additions are in a Crowdin-managed locale file. Keep manual key changes in
src/config/locales/en-US.jsononly, then let sync propagate translations.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration and should not be manually edited in pull requests.
Also applies to: 683-688, 1402-1405, 1419-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/uz-UZ.json` around lines 612 - 621, Remove the manual translation key additions from this Crowdin-managed locale file (the keys: "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed" and the other ranges noted) and instead add or update those keys only in en-US.json so Crowdin can propagate them; revert the changes in this non-en-US locale file and commit the key edits to en-US.json only.src/config/locales/ac-ace.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorPlease revert direct updates to this non-source locale file.
src/config/locales/ac-ace.jsonshould not be manually changed in key-introduction PRs. Keep key additions insrc/config/locales/en-US.jsononly and let Crowdin sync this locale.Based on learnings: In the ecency-mobile repository, only the
en-US.jsonlocale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration and should not be manually edited in pull requests.Also applies to: 683-688, 1402-1405, 1420-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/ac-ace.json` around lines 612 - 621, This PR inexplicably edits the generated locale file src/config/locales/ac-ace.json (e.g., keys like "operation_failed_with_reason", "wallet_refresh_failed", "boost_failed", "add_withdraw_route_failed", etc.); revert all manual changes in ac-ace.json and any other non-source locales (also referenced ranges 683-688, 1402-1405, 1420-1431), then add or update the new translation keys only in the source locale src/config/locales/en-US.json so Crowdin can propagate them automatically; ensure no manual edits remain in generated locale files before pushing.src/config/locales/tr-TR.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorThis locale file should not be manually changed in key rollout PRs.
Please remove the direct additions in
src/config/locales/tr-TR.jsonand keep translation key introduction limited tosrc/config/locales/en-US.json; Crowdin should propagate the rest.Based on learnings: In the ecency-mobile repository, only the
en-US.jsonlocale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration and should not be manually edited in pull requests.Also applies to: 683-688, 1402-1405, 1420-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/tr-TR.json` around lines 612 - 621, The new translation keys (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed") were added directly to tr-TR.json but should not be edited here; remove these entries from src/config/locales/tr-TR.json and instead introduce or update the corresponding keys only in src/config/locales/en-US.json so Crowdin can propagate translations automatically.src/config/locales/cs-CZ.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorAvoid manual locale edits outside
en-US.json.This non-
en-USlocale file is being edited directly. Per repo workflow, these keys should be introduced insrc/config/locales/en-US.jsonand synchronized via Crowdin, so these additions should be removed from this PR.Based on learnings: In the ecency-mobile repository, only the
en-US.jsonlocale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration and should not be manually edited in pull requests.Also applies to: 683-688, 1402-1405, 1420-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/cs-CZ.json` around lines 612 - 621, Revert the manual additions of translation keys in the cs-CZ.json locale (specifically keys like "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed" and the other key ranges noted) and instead add these keys only to src/config/locales/en-US.json so they will be propagated via Crowdin; ensure you remove the manual edits from non-en-US files in this PR and add new keys/updates to the en-US.json entry points (e.g., where other translation keys are defined) so localization sync remains correct.src/config/locales/bs-BA.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorRevert manual changes in Crowdin-managed locale file.
src/config/locales/bs-BA.jsonshould not be edited directly for new keys. Keep changes insrc/config/locales/en-US.jsonand rely on Crowdin synchronization for this locale.Based on learnings: In the ecency-mobile repository, only the
en-US.jsonlocale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration and should not be manually edited in pull requests.Also applies to: 683-688, 1402-1405, 1420-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/bs-BA.json` around lines 612 - 621, This locale file (src/config/locales/bs-BA.json) was manually edited and must be reverted to the Crowdin-synced state: remove the manual additions/changes such as "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed" (and the other sections noted at 683-688, 1402-1405, 1420-1431) and restore the file to the version managed by Crowdin; instead make any new or updated keys in src/config/locales/en-US.json so Crowdin can propagate them to bs-BA.json.src/config/locales/ko-KR.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorNon-
en-USlocale key additions should be excluded from this PR.These additions in
src/config/locales/ko-KR.jsonshould be synced from Crowdin rather than edited here directly. Please remove them and keep source-key changes insrc/config/locales/en-US.json.Based on learnings: In the ecency-mobile repository, only the
en-US.jsonlocale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration and should not be manually edited in pull requests.Also applies to: 683-688, 1402-1405, 1420-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/ko-KR.json` around lines 612 - 621, Remove the manually added translation keys from src/config/locales/ko-KR.json (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed" and the other blocks at the noted ranges 683-688, 1402-1405, 1420-1431) so this file remains unchanged, and instead add or update those keys only in the source locale file src/config/locales/en-US.json; keep ko-KR.json clean (no manual additions) because non-en-US locales are synchronized via Crowdin.src/config/locales/tg-TJ.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorThis locale file should not be manually edited in this PR flow.
Line 612 onward and Line 1419 onward introduce new keys directly in
src/config/locales/tg-TJ.json. Per repository workflow, key additions should be made only insrc/config/locales/en-US.json, then propagated by Crowdin.Based on learnings, in the ecency-mobile repository only
en-US.jsonshould be modified for translation keys, while other locale files are auto-synced via Crowdin and should not be manually edited in PRs.Also applies to: 683-688, 1402-1405, 1419-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/tg-TJ.json` around lines 612 - 621, The PR incorrectly adds new translation keys directly into src/config/locales/tg-TJ.json (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed" and the other keys noted); revert those manual edits in tg-TJ.json and instead add the new keys and English strings to src/config/locales/en-US.json only, then let Crowdin propagate translations to tg-TJ.json; ensure you remove the added keys from tg-TJ.json before committing and place all new keys into the en-US.json changeset.src/config/locales/as-IN.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorPlease keep these localization additions out of
as-IN.json.The new keys added at Line 612-621, Line 683-688, Line 1402-1405, and Line 1419-1431 should be authored in
src/config/locales/en-US.jsononly, then synced to this locale by Crowdin.Based on learnings, in the ecency-mobile repository only
en-US.jsonshould be modified for translation keys, while other locale files are auto-synced via Crowdin and should not be manually edited in PRs.Also applies to: 683-688, 1402-1405, 1419-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/as-IN.json` around lines 612 - 621, Remove the newly added translation keys (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed" and the other keys mentioned at the other ranges) from src/config/locales/as-IN.json and instead add them only to src/config/locales/en-US.json; after adding to en-US.json, leave as-IN.json unchanged so Crowdin can sync the translations automatically (do not manually edit other locale files in this PR).src/config/locales/sw-KE.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 Major
sw-KE.jsonedits should be reverted for this PR workflow.The key additions in Line 612-621, Line 683-688, Line 1402-1405, and Line 1419-1431 are manual locale updates in a non-
en-USfile. These should be sourced fromsrc/config/locales/en-US.jsonand synced via Crowdin instead.Based on learnings, in the ecency-mobile repository only
en-US.jsonshould be modified for translation keys, while other locale files are auto-synced via Crowdin and should not be manually edited in PRs.Also applies to: 683-688, 1402-1405, 1419-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/sw-KE.json` around lines 612 - 621, The sw-KE.json file contains manual additions/edits for keys like "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", and "market_data_load_failed" (and the other groups noted) that must be reverted; undo these changes in src/config/locales/sw-KE.json so it matches the last synced state, then add or update any new translation keys only in src/config/locales/en-US.json and trigger the normal Crowdin sync workflow (do not modify non-en-US locale files manually).src/config/locales/ru-RU.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorPlease avoid manual key updates in non-
en-USlocale files.Lines 612-621, 683-688, 1402-1405, and 1419-1431 add new translation keys directly in
src/config/locales/ru-RU.json. In this repo, these should be introduced only insrc/config/locales/en-US.json; other locale files are synchronized by Crowdin.Based on learnings, in the ecency-mobile repository only
en-US.jsonshould be modified for translation keys, while other locale files are auto-synced via Crowdin and should not be manually edited in PRs.Also applies to: 683-688, 1402-1405, 1419-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/ru-RU.json` around lines 612 - 621, The PR added new translation keys directly into ru-RU.json (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed" and the other keys noted in the comment); revert those manual additions from src/config/locales/ru-RU.json and instead add the new keys only to src/config/locales/en-US.json so Crowdin can propagate them to other locales automatically.src/config/locales/az-AZ.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorManual updates in
az-AZ.jsonconflict with the Crowdin sync workflow.The additions at Line 612-621, Line 683-688, Line 1402-1405, and Line 1419-1431 should be removed from this file and kept only in
src/config/locales/en-US.json.Based on learnings, in the ecency-mobile repository only
en-US.jsonshould be modified for translation keys, while other locale files are auto-synced via Crowdin and should not be manually edited in PRs.Also applies to: 683-688, 1402-1405, 1419-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/az-AZ.json` around lines 612 - 621, Remove the manually added translation keys in src/config/locales/az-AZ.json (specifically keys like "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed" and the other groups referenced at the same regions) so this file matches the Crowdin-synced state; keep any new or changed translation keys only in src/config/locales/en-US.json and revert the az-AZ.json edits (and the other listed ranges) to avoid manual edits that conflict with the Crowdin workflow.src/config/locales/en-US.json-683-688 (1)
683-688:⚠️ Potential issue | 🟠 MajorNew auth localization keys are not wired into the active auth-upgrade UI path.
src/providers/sdk/mobilePlatformAdapter.ts(Lines 153-169) still hardcodes English labels for the auth chooser, so these new keys won’t be used for localized users.Also applies to: 1420-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/en-US.json` around lines 683 - 688, The auth chooser UI in src/providers/sdk/mobilePlatformAdapter.ts currently uses hardcoded English labels; update the code that builds the chooser/modal (the block around the auth chooser at ~lines 153-169 and the similar block at ~1420-1431) to use the localization keys from en-US.json instead of literal strings. Replace the hardcoded titles/messages with localized lookups for "active_key_required_title", "active_key_required_message", "authorization_required_title", and "authorization_required_message", and replace the auth option labels with localized lookups for "auth_method_hiveauth" and "auth_method_hivesigner" using the project’s existing translation function (e.g., i18n.t or the app’s translate helper) so the chooser displays localized text for all supported languages.src/config/locales/bg-BG.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorAvoid manual edits to non-
en-US.jsonlocale filesThis PR directly modifies
src/config/locales/bg-BG.json, but these locale files are Crowdin-managed and should not be hand-edited in PRs. Please keep key additions insrc/config/locales/en-US.jsononly and let Crowdin propagate translations.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding/updating translation keys; other locale files are automatically synchronized via Crowdin and should not be manually edited.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/bg-BG.json` around lines 612 - 621, This change manually edited Crowdin-managed locale keys in bg-BG.json (eg. "operation_failed_with_reason", "wallet_refresh_failed", "boost_failed_with_reason", etc.); revert these edits in bg-BG.json and instead add or update the new/changed keys only in en-US.json (the canonical source), then let Crowdin handle translations for other locales—ensure no manual changes remain in bg-BG.json and commit only the en-US.json updates.src/config/locales/es-MX.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorPlease remove direct edits to
es-MX.jsonfrom this PRThis file should be updated through Crowdin sync, not manually in code review PRs. Keep translation key additions confined to
src/config/locales/en-US.json.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding/updating translation keys; other locale files are automatically synchronized via Crowdin and should not be manually edited.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/es-MX.json` around lines 612 - 621, This PR contains manual edits to the Spanish locale file (keys like "operation_failed_with_reason", "wallet_refresh_failed", "boost_failed_with_reason", "add_withdraw_route_failed", etc. in src/config/locales/es-MX.json); revert those changes in es-MX.json and instead add any new or updated translation keys to src/config/locales/en-US.json only (so Crowdin can sync translations), leaving non-English locale files untouched by the PR.src/config/locales/es-AR.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorThis locale file should not be manually changed in PRs
src/config/locales/es-AR.jsonis being edited directly. Per project workflow, translation key updates should be made insrc/config/locales/en-US.jsononly, with Crowdin handling the rest.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding/updating translation keys; other locale files are automatically synchronized via Crowdin and should not be manually edited.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/es-AR.json` around lines 612 - 621, The PR incorrectly modifies the es-AR.json locale file directly (you changed keys like "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed_with_reason", "add_withdraw_route_failed", etc.); revert those edits in es-AR.json and instead add or update the corresponding translation keys only in src/config/locales/en-US.json so Crowdin can propagate them to other locales, then remove the manual changes from the es-AR.json commit and leave localization synchronization to the Crowdin workflow.src/config/locales/pa-IN.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorNon-source locale edits should be excluded from this PR
src/config/locales/pa-IN.jsonis being manually edited, but this repo’s translation flow expects onlysrc/config/locales/en-US.jsonto be changed in PRs.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding/updating translation keys; other locale files are automatically synchronized via Crowdin and should not be manually edited.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/pa-IN.json` around lines 612 - 621, This PR contains manual edits to non-source locale keys (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "swap_failed", "market_data_load_failed") in pa-IN.json; revert those changes in pa-IN.json and instead apply any new or updated keys to the canonical en-US.json so the translation pipeline (Crowdin) can sync them to other locales, then remove the manual pa-IN.json edits from the commit.src/config/locales/pl-PL.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorPlease move these key additions to
en-US.jsononlyDirect edits in
src/config/locales/pl-PL.jsonbypass the repository’s Crowdin flow and risk being overwritten/out-of-sync. Add/update keys insrc/config/locales/en-US.jsononly.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding/updating translation keys; other locale files are automatically synchronized via Crowdin and should not be manually edited.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/pl-PL.json` around lines 612 - 621, The new translation keys (operation_failed_with_reason, wallet_refresh_failed, wallet_refresh_missing_account, boost_failed, boost_failed_with_reason, add_withdraw_route_failed, remove_withdraw_route_failed, update_tokens_failed, swap_failed, market_data_load_failed) were added directly to src/config/locales/pl-PL.json but must be added only to src/config/locales/en-US.json to preserve the Crowdin sync; revert/remove these additions from pl-PL.json and add the exact key/value pairs into en-US.json instead (use the same key names and English text), then commit the change so localization propagation happens via Crowdin rather than direct edits to pl-PL.json.
There was a problem hiding this comment.
Note
Due to the large number of review comments, Critical severity comments were prioritized as inline comments.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
src/config/locales/hi-IN.json (1)
612-1431:⚠️ Potential issue | 🟠 MajorPlease avoid manual edits in non-
en-USlocale files.This PR directly changes
src/config/locales/hi-IN.json. For key additions/updates, changes should be made only inen-US.json, then propagated via Crowdin sync. Please revert this file’s manual additions and keep source updates inen-US.jsononly.Based on learnings: In this repository, only
en-US.jsonshould be manually updated for translation keys; other locale files are auto-synchronized via Crowdin integration.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/hi-IN.json` around lines 612 - 1431, The hi-IN locale file was manually edited (new/updated translation keys such as "operation_failed_with_reason", "active_key_required_title", "auth_method_hiveauth", "auth_method_hivesigner", "active_key_required_message", etc. appear in the diff); revert these manual changes in the hi-IN JSON and instead add or update the corresponding keys only in en-US.json, then trigger the Crowdin sync/process to propagate translations to hi-IN so translations remain managed by the localization pipeline.src/config/locales/eo-UY.json (1)
1-1433:⚠️ Potential issue | 🟠 MajorAvoid direct edits in non-
en-US.jsonlocale files.This PR updates
src/config/locales/eo-UY.json. Per project workflow, translation key additions/updates should be made insrc/config/locales/en-US.jsononly, with other locale files synced by Crowdin. Please revert manual changes here (or explicitly confirm this PR is Crowdin-generated sync output).Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; other locale files are automatically synchronized via Crowdin integration and should not be manually edited in pull requests.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/eo-UY.json` around lines 1 - 1433, You modified a non-english locale (keys under top-level objects like "profile", "post_poll", "posting_authority", etc.) — revert these manual edits in eo-UY.json and restore the file to the pre-PR state (undo your changes or reset the file to the branch HEAD) so only en-US.json is the source of truth for new/updated translation keys; if this file truly is Crowdin-generated output, instead mark the PR as Crowdin sync output in the PR description and include an explicit confirmation message so maintainers know it should not be manually edited.
🟡 Minor comments (1)
src/config/locales/ru-RU.json-612-621 (1)
612-621:⚠️ Potential issue | 🟡 MinorNew Russian-locale entries are untranslated (English text).
Lines in these ranges add user-facing strings in English inside
ru-RU.json, which will produce mixed-language UI for Russian users.Also applies to: 683-688, 1402-1405, 1421-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/ru-RU.json` around lines 612 - 621, The new Russian locale entries are still in English; translate each key's string value into Russian (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed") so the ru-RU.json contains Russian user-facing text, and apply the same translations check for the other reported ranges (around keys in lines ~683-688, ~1402-1405, and ~1421-1431) to avoid mixed-language UI. Ensure placeholders like {operation} and {reason} remain intact and punctuation/style match existing Russian locale conventions.
🧹 Nitpick comments (1)
src/config/locales/vi-VN.json (1)
683-688: Consider consolidating duplicated auth-copy keys to reduce drift risk.Line 683-688 (
alert.*) and Line 1420-1431 (auth_upgrade.*) carry overlapping authorization messaging. Prefer a single namespace for shared copy to avoid future inconsistency across flows.Also applies to: 1420-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/vi-VN.json` around lines 683 - 688, The alert copy for authorization is duplicated across keys like active_key_required_title, active_key_required_message, authorization_required_title, authorization_required_message, auth_method_hiveauth, and auth_method_hivesigner (and the similar auth_upgrade.* keys); consolidate these into a single shared namespace (e.g., "auth.common.*") and update callers to reference the new shared keys instead of duplicated alert.* or auth_upgrade.* keys so there's one source of truth for all authorization messages to avoid drift.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Outside diff comments:
In `@src/config/locales/eo-UY.json`:
- Around line 1-1433: You modified a non-english locale (keys under top-level
objects like "profile", "post_poll", "posting_authority", etc.) — revert these
manual edits in eo-UY.json and restore the file to the pre-PR state (undo your
changes or reset the file to the branch HEAD) so only en-US.json is the source
of truth for new/updated translation keys; if this file truly is
Crowdin-generated output, instead mark the PR as Crowdin sync output in the PR
description and include an explicit confirmation message so maintainers know it
should not be manually edited.
In `@src/config/locales/hi-IN.json`:
- Around line 612-1431: The hi-IN locale file was manually edited (new/updated
translation keys such as "operation_failed_with_reason",
"active_key_required_title", "auth_method_hiveauth", "auth_method_hivesigner",
"active_key_required_message", etc. appear in the diff); revert these manual
changes in the hi-IN JSON and instead add or update the corresponding keys only
in en-US.json, then trigger the Crowdin sync/process to propagate translations
to hi-IN so translations remain managed by the localization pipeline.
---
Major comments:
In `@src/config/locales/ac-ace.json`:
- Around line 612-621: Remove the manually added localization keys (e.g.,
"operation_failed_with_reason", "wallet_refresh_failed",
"wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", "remove_withdraw_route_failed",
"update_tokens_failed", "swap_failed", "market_data_load_failed" and the other
ranges noted) from this locale file and instead add or update those keys only in
the master locale en-US.json; then propagate translations via the Crowdin sync
process so other locale files (including this one) are updated automatically.
In `@src/config/locales/az-AZ.json`:
- Around line 612-621: Remove the newly added localization keys from the
az-AZ.json file and instead add the same keys and English values into the single
source en-US.json; specifically move keys like "operation_failed_with_reason",
"wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed",
"boost_failed_with_reason", "add_withdraw_route_failed",
"remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", and
"market_data_load_failed" (and the other keys referenced in the comment) into
src/config/locales/en-US.json, commit only the en-US.json changes, and leave
other locale files (including az-AZ.json) untouched so Crowdin can propagate
translations.
In `@src/config/locales/bg-BG.json`:
- Around line 612-621: These translations were edited directly in
src/config/locales/bg-BG.json (keys like "operation_failed_with_reason",
"wallet_refresh_failed", "boost_failed_with_reason", etc.); revert these manual
edits and instead add or update the corresponding keys only in
src/config/locales/en-US.json so Crowdin can propagate them to bg-BG.json, and
remove any other direct changes to bg-BG.json referenced in the comment (lines
~683-688, 1402-1405, 1420-1431).
In `@src/config/locales/bn-BD.json`:
- Around line 612-621: This PR contains manual changes in the Bengali locale
file (bn-BD.json) — remove the manually added/edited keys (e.g.,
"operation_failed_with_reason", "wallet_refresh_failed",
"boost_failed_with_reason", "add_withdraw_route_failed", etc.) from
src/config/locales/bn-BD.json and revert that file to the Crowdin-synced state;
instead add or update the corresponding keys only in
src/config/locales/en-US.json (ensuring the exact key names are present) and
then trigger or request the Crowdin sync so translations propagate to bn-BD.json
rather than committing manual edits directly to non-en-US locale files.
In `@src/config/locales/bo-BT.json`:
- Around line 612-621: Revert the manual edits made to the bo-BT locale (undo
additions/changes to keys like "operation_failed_with_reason",
"wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed",
"boost_failed_with_reason", "add_withdraw_route_failed",
"remove_withdraw_route_failed", "update_tokens_failed", "swap_failed",
"market_data_load_failed" and the other affected ranges) so bo-BT matches the
repo’s synced state; make any intended key additions or modifications in
src/config/locales/en-US.json only, then let Crowdin propagate the changes to
bo-BT rather than committing direct edits to bo-BT.json.
In `@src/config/locales/bs-BA.json`:
- Around line 612-621: You modified non-source locale
src/config/locales/bs-BA.json directly (added keys like
"operation_failed_with_reason", "wallet_refresh_failed",
"wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", "remove_withdraw_route_failed",
"update_tokens_failed", "swap_failed", "market_data_load_failed") — revert these
edits in bs-BA.json and instead add the new keys and English strings to
src/config/locales/en-US.json so they enter the localization workflow; also
apply the same revert/add pattern for the other manual edits noted around the
ranges referenced (683-688, 1402-1405, 1419-1431) to ensure only en-US.json is
changed and Crowdin will propagate translations.
In `@src/config/locales/ca-ES.json`:
- Around line 612-621: You modified translation keys directly in ca-ES.json
(e.g., "operation_failed_with_reason", "wallet_refresh_failed",
"boost_failed_with_reason", "add_withdraw_route_failed", "swap_failed",
"market_data_load_failed"); revert those edits in ca-ES.json and instead add or
update the corresponding keys only in en-US.json so Crowdin can propagate
translations, ensuring any new keys are present in en-US.json and removing
manual changes from ca-ES.json (also undo similar manual edits at the other
referenced ranges).
In `@src/config/locales/ceb-PH.json`:
- Around line 612-621: This PR contains manual edits to localized keys (e.g.,
"operation_failed_with_reason", "wallet_refresh_failed",
"wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", "remove_withdraw_route_failed",
"update_tokens_failed", "swap_failed", "market_data_load_failed" and the other
ranges noted); revert those changes in ceb-PH.json and instead add or update the
source keys only in src/config/locales/en-US.json so Crowdin can propagate
translations automatically, then remove the manual edits from other locale files
before merging.
In `@src/config/locales/cs-CZ.json`:
- Around line 612-621: Revert the direct translation key edits in cs-CZ.json
(e.g., keys like "operation_failed_with_reason", "wallet_refresh_failed",
"boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed",
"remove_withdraw_route_failed", "update_tokens_failed", "swap_failed",
"market_data_load_failed" and the other mentioned keys) back to their previous
Crowdin-synced state, and instead apply any new or changed keys/schema only in
src/config/locales/en-US.json so the Crowdin workflow can propagate
translations; do not commit direct changes to other locale files and ensure no
schema/key additions remain in cs-CZ.json before pushing.
In `@src/config/locales/da-DK.json`:
- Around line 612-621: The new translation keys (e.g.,
"operation_failed_with_reason", "wallet_refresh_failed",
"wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", "remove_withdraw_route_failed",
"update_tokens_failed", "swap_failed", "market_data_load_failed") were added
directly to da-DK.json but this file is Crowdin-synced — revert these additions
from da-DK.json and instead add or update the keys in
src/config/locales/en-US.json (the single source of truth); also remove any
other manual key additions you made elsewhere in da-DK.json so only en-US.json
contains the new/changed keys and let Crowdin propagate translations to other
locale files.
In `@src/config/locales/de-DE.json`:
- Around line 612-621: The new localization keys you added
("operation_failed_with_reason", "wallet_refresh_failed",
"wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", "remove_withdraw_route_failed",
"update_tokens_failed", "swap_failed", "market_data_load_failed" and the other
keys mentioned) must be defined only in src/config/locales/en-US.json; remove
these additions from src/config/locales/de-DE.json (and any other non-en-US
files) and add them to en-US.json instead so Crowdin can propagate translations
automatically; ensure you do not manually edit other locale files in this PR and
keep en-US.json as the single source of truth for new/updated keys.
In `@src/config/locales/el-GR.json`:
- Around line 612-621: These new translation keys (e.g.,
"operation_failed_with_reason", "wallet_refresh_failed",
"wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", "remove_withdraw_route_failed",
"update_tokens_failed", "swap_failed", "market_data_load_failed" and the other
ranges noted) must not be added directly to the non-source locale file; instead
add these keys and their English values to the source locale file
(src/config/locales/en-US.json) and then let the Crowdin sync process propagate
them to el-GR.json; revert/remove these direct edits from
src/config/locales/el-GR.json so only the en-US.json contains the new keys and
translations are updated via the established localization workflow.
In `@src/config/locales/es-AR.json`:
- Around line 612-621: You modified localized keys (e.g.,
"operation_failed_with_reason", "wallet_refresh_failed",
"boost_failed_with_reason", "add_withdraw_route_failed", etc.) directly in
es-AR.json; revert these manual edits and instead add or update the keys only in
src/config/locales/en-US.json so Crowdin can propagate translations
automatically, then remove any other manual changes you made in the non-en-US
locale files (also covering the other referenced ranges) and let the CI/Crowdin
sync handle translations.
In `@src/config/locales/es-MX.json`:
- Around line 612-621: The PR added new localization keys directly into
es-MX.json (e.g., "operation_failed_with_reason", "wallet_refresh_failed",
"wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", "remove_withdraw_route_failed",
"update_tokens_failed", "swap_failed", "market_data_load_failed"); remove these
additions from src/config/locales/es-MX.json and instead add the same keys and
English values to src/config/locales/en-US.json so en-US.json remains the single
source of truth; leave other locale files unchanged (Crowdin will propagate
translations) and commit only the en-US.json change.
In `@src/config/locales/et-EE.json`:
- Around line 612-621: This file contains manual edits to localized keys—revert
the changes in src/config/locales/et-EE.json for the keys shown (e.g.,
"operation_failed_with_reason", "wallet_refresh_failed",
"wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", "remove_withdraw_route_failed",
"update_tokens_failed", "swap_failed", "market_data_load_failed") and any other
manually edited keys referenced in the review; instead, make/add/update these
translation keys only in src/config/locales/en-US.json so Crowdin can propagate
translations automatically, and ensure et-EE.json remains identical to the
auto-synced source (restore from repo state or remove the manual entries).
In `@src/config/locales/fa-IR.json`:
- Around line 612-621: This change manually edits non-en-US locale file
fa-IR.json (e.g., keys like "operation_failed_with_reason",
"wallet_refresh_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", etc.); revert these manual edits in
src/config/locales/fa-IR.json and instead make the key additions/updates in
src/config/locales/en-US.json only, then let Crowdin propagate translations to
fa-IR.json; ensure you remove the duplicated manual entries from fa-IR.json so
only Crowdin-managed content remains.
In `@src/config/locales/fi-FI.json`:
- Around line 612-621: This change adds new translation keys directly to
fi-FI.json which should not be the source-of-truth; revert the additions in
src/config/locales/fi-FI.json (e.g., keys like "operation_failed_with_reason",
"wallet_refresh_failed", "boost_failed", "add_withdraw_route_failed",
"remove_withdraw_route_failed", "update_tokens_failed", "swap_failed",
"market_data_load_failed" and the other mentioned ranges) and instead add these
keys to the canonical en-US.json so Crowdin can propagate them to other locales;
ensure you only modify en-US.json for new/updated keys and remove any direct
edits to locale files other than en-US.json.
In `@src/config/locales/fil-PH.json`:
- Around line 612-621: These locale keys (e.g., "operation_failed_with_reason",
"wallet_refresh_failed", "boost_failed", "add_withdraw_route_failed",
"market_data_load_failed", etc.) were added directly into fil-PH.json; revert
these manual additions and instead add or update the keys only in
src/config/locales/en-US.json so the Crowdin sync can propagate them to
derivative locales, then remove the identical entries from fil-PH.json (unless
this PR is the automated Crowdin sync) to comply with the localization workflow.
In `@src/config/locales/fr-FR.json`:
- Around line 612-621: The changes add new translation keys directly into
fr-FR.json (e.g., "operation_failed_with_reason", "wallet_refresh_failed",
"wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", "remove_withdraw_route_failed",
"update_tokens_failed", "swap_failed", "market_data_load_failed"); instead,
revert these edits in fr-FR.json and add or update the same keys only in
en-US.json so Crowdin can propagate them to other locales (apply the same fix
for the other ranges called out: 683-688, 1402-1405, 1419-1431), or keep them in
fr-FR.json only if this PR is the automated Crowdin sync; ensure you reference
the exact key names above when moving the entries.
In `@src/config/locales/ga-IE.json`:
- Around line 612-621: The new localization keys (e.g.,
"operation_failed_with_reason", "wallet_refresh_failed",
"wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", "remove_withdraw_route_failed",
"update_tokens_failed", "swap_failed", "market_data_load_failed" — and the other
keys you added in the ranges noted) were added directly to
src/config/locales/ga-IE.json; instead, add or update these keys only in
src/config/locales/en-US.json and remove them from ga-IE.json so Crowdin can
propagate translations; locate the added key names in ga-IE.json, delete those
entries, add the same key/value pairs to en-US.json (ensuring JSON syntax),
commit the change, and leave other locale files untouched.
In `@src/config/locales/gl-ES.json`:
- Around line 612-621: Revert the manual additions in
src/config/locales/gl-ES.json — specifically remove the keys added here like
"operation_failed_with_reason", "wallet_refresh_failed",
"wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", "remove_withdraw_route_failed",
"update_tokens_failed", "swap_failed", and "market_data_load_failed" (and the
other manual edits noted around the other ranges) so that only en-US.json is the
source of new/changed translation keys; ensure any intended key changes are
instead made in en-US.json and let Crowdin/sync update gl-ES.json rather than
committing direct edits to gl-ES.json.
In `@src/config/locales/got-DE.json`:
- Around line 612-621: Revert the manual additions in
src/config/locales/got-DE.json (the added keys like
"operation_failed_with_reason", "wallet_refresh_failed",
"boost_failed_with_reason", etc.) so that this file matches the Crowdin-synced
state; undo the direct edits or restore the file from the previous
commit/Crowdin export, and ensure new/updated translation keys are only added to
en-US.json going forward so Crowdin can propagate them to other locales (also
check and revert the similar manual changes referenced around the other ranges
noted).
In `@src/config/locales/hr-HR.json`:
- Around line 612-621: Revert the direct additions to
src/config/locales/hr-HR.json (the new keys like "operation_failed_with_reason",
"wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed",
"boost_failed_with_reason", "add_withdraw_route_failed",
"remove_withdraw_route_failed", "update_tokens_failed", "swap_failed",
"market_data_load_failed" and the other keys added in the ranges called out) so
the non-en locale is unchanged, and instead add any new or updated translation
keys only to src/config/locales/en-US.json (so Crowdin will propagate them);
ensure you remove the edits from hr-HR.json in all referenced ranges (612-621,
683-688, 1402-1405, 1420-1431) and commit only the en-US.json changes.
In `@src/config/locales/hy-AM.json`:
- Around line 612-621: The new translation keys were added directly to
src/config/locales/hy-AM.json (e.g., "operation_failed_with_reason",
"wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed",
"boost_failed_with_reason", "add_withdraw_route_failed",
"remove_withdraw_route_failed", "update_tokens_failed", "swap_failed",
"market_data_load_failed" and the other keys referenced at lines 683, 1402,
1420); remove these additions from hy-AM.json and instead add the keys only to
src/config/locales/en-US.json so Crowdin can propagate them to other locales,
keeping hy-AM.json unchanged except for Crowdin-synced updates.
In `@src/config/locales/it-IT.json`:
- Around line 612-621: This PR edited translated keys directly (e.g.,
"operation_failed_with_reason", "wallet_refresh_failed", "boost_failed",
"add_withdraw_route_failed", "remove_withdraw_route_failed",
"update_tokens_failed", "swap_failed", "market_data_load_failed"); revert those
manual edits in the non-en-US locale (it-IT) and instead apply the key changes
to the canonical en-US locale file (or confirm that this PR is an automated
Crowdin sync import), then remove any accidental direct changes in other ranges
noted (lines referenced around 683-688 and 1402-1431) so all non-en-US files
remain synced via Crowdin only.
In `@src/config/locales/ja-JP.json`:
- Around line 612-621: Revert the manual edits in src/config/locales/ja-JP.json
(remove changes to keys such as "operation_failed_with_reason",
"wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed",
"boost_failed_with_reason", "add_withdraw_route_failed",
"remove_withdraw_route_failed", "update_tokens_failed", "swap_failed",
"market_data_load_failed" and the other ranges noted) so the file matches the
Crowdin-synchronized copy, and instead apply any new or changed translation keys
only to src/config/locales/en-US.json; do not modify other locale files (e.g.,
the ranges referenced 683-688, 1402-1405, 1420-1431) in this PR.
In `@src/config/locales/ko-KR.json`:
- Around line 612-621: This PR incorrectly adds translation keys directly to
src/config/locales/ko-KR.json (e.g., "operation_failed_with_reason",
"wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed",
"boost_failed_with_reason", "add_withdraw_route_failed",
"remove_withdraw_route_failed", "update_tokens_failed", "swap_failed",
"market_data_load_failed" and other ranges noted) — revert those changes in
ko-KR.json so it stays read-only, then add or update the new/changed keys in
src/config/locales/en-US.json instead and let Crowdin propagate translations;
ensure you remove any direct edits to ko-KR.json before finalizing the commit.
In `@src/config/locales/ky-KG.json`:
- Around line 612-621: Revert the direct edits to src/config/locales/ky-KG.json
(remove the added keys like "operation_failed_with_reason",
"wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed",
"boost_failed_with_reason", "add_withdraw_route_failed",
"remove_withdraw_route_failed", "update_tokens_failed", "swap_failed",
"market_data_load_failed") and instead add those new translation keys and values
into src/config/locales/en-US.json so Crowdin can propagate them; ensure you
only modify en-US.json for new/updated keys and leave other locale files
untouched.
In `@src/config/locales/lt-LT.json`:
- Around line 612-621: Remove the manual additions in
src/config/locales/lt-LT.json for the new translation keys (e.g.,
"operation_failed_with_reason", "wallet_refresh_failed",
"wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", "remove_withdraw_route_failed",
"update_tokens_failed", "swap_failed", "market_data_load_failed" and the other
ranges mentioned) — do not add keys directly to non-en-US locale files; instead
add or update the canonical keys in src/config/locales/en-US.json and let
Crowdin propagate translations to lt-LT.json via the automated sync, removing
the direct edits from lt-LT.json unless this PR is the Crowdin sync output.
In `@src/config/locales/mn-MN.json`:
- Around line 612-621: Revert the manual additions in
src/config/locales/mn-MN.json by removing the newly-added keys shown (e.g.,
"operation_failed_with_reason", "wallet_refresh_failed",
"wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", "remove_withdraw_route_failed",
"update_tokens_failed", "swap_failed", "market_data_load_failed") and any other
manually-added keys referenced in the review; instead add or update these keys
only in src/config/locales/en-US.json (the canonical source) so Crowdin can
synchronize translations for mn-MN.json, and ensure no other locale files are
edited directly.
In `@src/config/locales/ne-NP.json`:
- Around line 612-621: The translations shown (keys:
operation_failed_with_reason, wallet_refresh_failed,
wallet_refresh_missing_account, boost_failed, boost_failed_with_reason,
add_withdraw_route_failed, remove_withdraw_route_failed, update_tokens_failed,
swap_failed, market_data_load_failed and the other referenced ranges) were
edited in a non-primary locale; revert these manual edits from the ne-NP.json
changes and instead add or update the same keys and values in en-US.json (the
canonical source) so Crowdin can propagate them; locate these keys in the diff
by their exact key names and make the changes only in en-US.json, leaving other
locale files untouched.
In `@src/config/locales/nl-NL.json`:
- Around line 612-621: This change adds new translation keys directly into
nl-NL.json (e.g., "operation_failed_with_reason", "wallet_refresh_failed",
"boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed",
"remove_withdraw_route_failed", "update_tokens_failed", "swap_failed",
"market_data_load_failed") which violates the workflow; remove these entries
from src/config/locales/nl-NL.json and instead add the new keys and English
values to src/config/locales/en-US.json, then trigger or request a Crowdin sync
so other locales (including nl-NL) are populated automatically.
In `@src/config/locales/pa-IN.json`:
- Around line 612-621: Revert any manual changes made to the pa-IN locale file
for the keys listed (e.g., "operation_failed_with_reason",
"wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed",
"boost_failed_with_reason", "add_withdraw_route_failed",
"remove_withdraw_route_failed", "update_tokens_failed", "swap_failed",
"market_data_load_failed" and the other ranges referenced) and instead add or
update these keys only in src/config/locales/en-US.json so Crowdin can propagate
translations; ensure pa-IN.json is restored to its previous commit state and
confirm new/updated keys exist in en-US.json (not in pa-IN.json) before pushing.
In `@src/config/locales/ru-RU.json`:
- Around line 612-621: The PR modifies translation keys directly in ru-RU.json
(keys like "operation_failed_with_reason", "wallet_refresh_failed",
"boost_failed_with_reason", "add_withdraw_route_failed", etc.); revert those
manual changes in src/config/locales/ru-RU.json and instead add or update the
same keys only in src/config/locales/en-US.json so Crowdin can propagate them to
other locales, then remove any direct edits to ru-RU.json from this branch
before re-submitting.
In `@src/config/locales/sa-IN.json`:
- Around line 612-621: This PR illegally includes manual edits to the
Crowdin-managed locale file src/config/locales/sa-IN.json (e.g., keys like
"operation_failed_with_reason", "wallet_refresh_failed",
"boost_failed_with_reason", "add_withdraw_route_failed", etc. and the other
ranges referenced); revert all changes in sa-IN.json back to the repository
version and ensure any new/updated translation keys are added only to
src/config/locales/en-US.json (leave all non-en-US locale files untouched), then
remove the sa-IN.json hunks from the commit so only en-US.json contains the
source-key updates.
In `@src/config/locales/sk-SK.json`:
- Around line 612-621: You added new translation keys directly into sk-SK.json
(e.g. "operation_failed_with_reason", "wallet_refresh_failed", "boost_failed",
etc.); revert those changes in sk-SK.json and instead add or update the new keys
only in src/config/locales/en-US.json (so the translations propagate via
Crowdin), leaving sk-SK.json untouched; ensure the same set of keys you intended
to add are present in en-US.json and remove any manual edits to other locale
files mentioned (lines around 683-688, 1402-1405, 1419-1431) so localization
stays managed by the Crowdin sync.
In `@src/config/locales/sl-SI.json`:
- Around line 612-621: This change manually adds new translation keys to
sl-SI.json (e.g., "operation_failed_with_reason", "wallet_refresh_failed",
"wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", "remove_withdraw_route_failed",
"update_tokens_failed", "swap_failed", "market_data_load_failed" and the other
keys referenced in lines 683-688, 1402-1405, 1419-1431); revert those edits in
src/config/locales/sl-SI.json so this file matches the sourced Crowdin state,
and instead add the new keys only to src/config/locales/en-US.json (copy the
exact key names and default English messages), leaving other locale files
untouched so Crowdin can propagate translations.
In `@src/config/locales/sv-SE.json`:
- Around line 612-621: Revert the manual key additions in the sv-SE.json locale
by removing the newly added keys (e.g., "operation_failed_with_reason",
"wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed",
"boost_failed_with_reason", "add_withdraw_route_failed",
"remove_withdraw_route_failed", "update_tokens_failed", "swap_failed",
"market_data_load_failed") from sv-SE.json and instead add those keys to
en-US.json (with their English messages); keep sv-SE.json untouched so Crowdin
can sync translations, then commit only the change to en-US.json.
In `@src/config/locales/ta-IN.json`:
- Around line 612-621: The new/updated translation keys (e.g.,
"operation_failed_with_reason", "wallet_refresh_failed",
"wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", "remove_withdraw_route_failed",
"update_tokens_failed", "swap_failed", "market_data_load_failed" and the other
keys referenced at the other ranges) should not be edited directly in
ta-IN.json; instead add or update these keys only in
src/config/locales/en-US.json and remove them from ta-IN.json so Crowdin can
sync translations automatically; update en-US.json with the exact key names and
English values, delete the manual entries in ta-IN.json (including the other
mentioned key groups), and leave ta-IN.json to be managed by the Crowdin sync
process.
In `@src/config/locales/th-TH.json`:
- Around line 612-621: Remove the manual translation-key additions from
th-TH.json and instead add or update those keys in en-US.json so Crowdin can
propagate them; specifically revert/delete the new keys like
"operation_failed_with_reason", "wallet_refresh_failed",
"wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", "remove_withdraw_route_failed",
"update_tokens_failed", "swap_failed", and "market_data_load_failed" (and the
other ranges noted: 683-688, 1403-1405, 1420-1431) from
src/config/locales/th-TH.json, then place the authoritative changes into
src/config/locales/en-US.json (or confirm this PR is the Crowdin sync PR and
leave a note indicating that), so other locales remain synced via Crowdin.
In `@src/config/locales/tk-TM.json`:
- Around line 612-621: The tk-TM.json file contains manual English entries that
were added directly (e.g., "operation_failed_with_reason",
"wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed",
"boost_failed_with_reason", "add_withdraw_route_failed",
"remove_withdraw_route_failed", "update_tokens_failed", "swap_failed",
"market_data_load_failed"); remove these manual changes from
src/config/locales/tk-TM.json and instead add these keys only to
src/config/locales/en-US.json so Crowdin can propagate them to other locales
automatically, ensuring no non-en-US locale files are edited directly.
In `@src/config/locales/tr-TR.json`:
- Around line 612-621: The new localization keys (operation_failed_with_reason,
wallet_refresh_failed, wallet_refresh_missing_account, boost_failed,
boost_failed_with_reason, add_withdraw_route_failed,
remove_withdraw_route_failed, update_tokens_failed, swap_failed,
market_data_load_failed and the other keys added in the same PR) were added
directly to src/config/locales/tr-TR.json; instead, remove these key additions
from tr-TR.json and add them only to src/config/locales/en-US.json (use the same
key names and English values), then save tr-TR.json without those manual
additions so Crowdin can propagate translations automatically.
In `@src/config/locales/uz-UZ.json`:
- Around line 612-621: You added new/updated translation keys directly in a
non-en-US locale (keys like "operation_failed_with_reason",
"wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed",
"boost_failed_with_reason", "add_withdraw_route_failed",
"remove_withdraw_route_failed", "update_tokens_failed", "swap_failed",
"market_data_load_failed"); revert those manual changes in the uz-UZ.json file
(and any other manual edits in this file corresponding to the other groups
mentioned) and instead add or update these keys only in en-US.json so they can
be propagated via Crowdin; remove the duplicated entries from the non-English
locale commit and ensure future changes follow the workflow of updating
en-US.json then syncing translations through Crowdin.
In `@src/config/locales/zh-CN.json`:
- Around line 612-621: The new translation keys (e.g.,
"operation_failed_with_reason", "wallet_refresh_failed",
"wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", "remove_withdraw_route_failed",
"update_tokens_failed", "swap_failed", "market_data_load_failed" and the other
keys in the noted ranges) should not be edited directly in zh-CN.json; instead
add or update these keys only in en-US.json so Crowdin can propagate the changes
to zh-CN.json automatically—revert any manual edits in zh-CN.json and ensure the
canonical additions/updates are present in en-US.json.
In `@src/config/locales/zh-TW.json`:
- Around line 612-621: The zh-TW locale file was edited directly to add
translation keys (e.g., "operation_failed_with_reason", "wallet_refresh_failed",
"boost_failed_with_reason", "add_withdraw_route_failed",
"remove_withdraw_route_failed", "update_tokens_failed", "swap_failed",
"market_data_load_failed"); instead, add these new keys and their English
strings to src/config/locales/en-US.json only, then remove the manual additions
from zh-TW.json so Crowdin can propagate translations; update en-US.json with
the same key names and values shown in the diff, leave other locale files
unchanged, and ensure no other manual edits remain at the other indicated ranges
(683-688, 1402-1405, 1419-1431).
---
Minor comments:
In `@src/config/locales/ru-RU.json`:
- Around line 612-621: The new Russian locale entries are still in English;
translate each key's string value into Russian (e.g.,
"operation_failed_with_reason", "wallet_refresh_failed",
"wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", "remove_withdraw_route_failed",
"update_tokens_failed", "swap_failed", "market_data_load_failed") so the
ru-RU.json contains Russian user-facing text, and apply the same translations
check for the other reported ranges (around keys in lines ~683-688, ~1402-1405,
and ~1421-1431) to avoid mixed-language UI. Ensure placeholders like {operation}
and {reason} remain intact and punctuation/style match existing Russian locale
conventions.
---
Nitpick comments:
In `@src/config/locales/vi-VN.json`:
- Around line 683-688: The alert copy for authorization is duplicated across
keys like active_key_required_title, active_key_required_message,
authorization_required_title, authorization_required_message,
auth_method_hiveauth, and auth_method_hivesigner (and the similar auth_upgrade.*
keys); consolidate these into a single shared namespace (e.g., "auth.common.*")
and update callers to reference the new shared keys instead of duplicated
alert.* or auth_upgrade.* keys so there's one source of truth for all
authorization messages to avoid drift.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: dbff3ec0-f332-4834-936e-ebaa458b34b4
📒 Files selected for processing (77)
src/config/locales/ac-ace.jsonsrc/config/locales/ar-SA.jsonsrc/config/locales/as-IN.jsonsrc/config/locales/az-AZ.jsonsrc/config/locales/bg-BG.jsonsrc/config/locales/bn-BD.jsonsrc/config/locales/bo-BT.jsonsrc/config/locales/bs-BA.jsonsrc/config/locales/ca-ES.jsonsrc/config/locales/ceb-PH.jsonsrc/config/locales/cs-CZ.jsonsrc/config/locales/da-DK.jsonsrc/config/locales/de-DE.jsonsrc/config/locales/el-GR.jsonsrc/config/locales/en-US.jsonsrc/config/locales/eo-UY.jsonsrc/config/locales/es-AR.jsonsrc/config/locales/es-ES.jsonsrc/config/locales/es-MX.jsonsrc/config/locales/et-EE.jsonsrc/config/locales/fa-IR.jsonsrc/config/locales/fi-FI.jsonsrc/config/locales/fil-PH.jsonsrc/config/locales/fr-FR.jsonsrc/config/locales/ga-IE.jsonsrc/config/locales/gl-ES.jsonsrc/config/locales/got-DE.jsonsrc/config/locales/he-IL.jsonsrc/config/locales/hi-IN.jsonsrc/config/locales/hr-HR.jsonsrc/config/locales/hu-HU.jsonsrc/config/locales/hy-AM.jsonsrc/config/locales/id-ID.jsonsrc/config/locales/is-IS.jsonsrc/config/locales/it-IT.jsonsrc/config/locales/ja-JP.jsonsrc/config/locales/ka-GE.jsonsrc/config/locales/kab-KAB.jsonsrc/config/locales/kk-KZ.jsonsrc/config/locales/ko-KR.jsonsrc/config/locales/ks-IN.jsonsrc/config/locales/ku-TR.jsonsrc/config/locales/ky-KG.jsonsrc/config/locales/lt-LT.jsonsrc/config/locales/lv-LV.jsonsrc/config/locales/mk-MK.jsonsrc/config/locales/mn-MN.jsonsrc/config/locales/ms-MY.jsonsrc/config/locales/ne-NP.jsonsrc/config/locales/nl-NL.jsonsrc/config/locales/no-NO.jsonsrc/config/locales/pa-IN.jsonsrc/config/locales/pcm-NG.jsonsrc/config/locales/pl-PL.jsonsrc/config/locales/pt-PT.jsonsrc/config/locales/ro-RO.jsonsrc/config/locales/ru-RU.jsonsrc/config/locales/sa-IN.jsonsrc/config/locales/sk-SK.jsonsrc/config/locales/sl-SI.jsonsrc/config/locales/sq-AL.jsonsrc/config/locales/sr-CS.jsonsrc/config/locales/sv-SE.jsonsrc/config/locales/sw-KE.jsonsrc/config/locales/ta-IN.jsonsrc/config/locales/tg-TJ.jsonsrc/config/locales/th-TH.jsonsrc/config/locales/tk-TM.jsonsrc/config/locales/tr-TR.jsonsrc/config/locales/uk-UA.jsonsrc/config/locales/ur-IN.jsonsrc/config/locales/ur-PK.jsonsrc/config/locales/uz-UZ.jsonsrc/config/locales/vi-VN.jsonsrc/config/locales/yo-NG.jsonsrc/config/locales/zh-CN.jsonsrc/config/locales/zh-TW.json
🚧 Files skipped from review as they are similar to previous changes (15)
- src/config/locales/kk-KZ.json
- src/config/locales/ar-SA.json
- src/config/locales/pl-PL.json
- src/config/locales/ka-GE.json
- src/config/locales/id-ID.json
- src/config/locales/pt-PT.json
- src/config/locales/es-ES.json
- src/config/locales/yo-NG.json
- src/config/locales/sr-CS.json
- src/config/locales/uk-UA.json
- src/config/locales/as-IN.json
- src/config/locales/ku-TR.json
- src/config/locales/no-NO.json
- src/config/locales/he-IL.json
- src/config/locales/lv-LV.json
There was a problem hiding this comment.
Note
Due to the large number of review comments, Critical severity comments were prioritized as inline comments.
🟡 Minor comments (1)
src/config/locales/hu-HU.json-684-686 (1)
684-686:⚠️ Potential issue | 🟡 MinorFix placeholder naming inconsistency in localization strings.
The localization files contain an inconsistency in placeholder naming. Lines 684 and 686 in
hu-HU.json(and all other locale files) use{requiredAuthority}for the authority placeholder, while line 1422 uses{authority}for the same concept. This inconsistency should be standardized—recommend changing line 1422 from{authority}to{requiredAuthority}to match the naming convention used in the other alert messages across all locale files.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/hu-HU.json` around lines 684 - 686, Localization placeholders are inconsistent: some messages use {requiredAuthority} while another uses {authority}; update the message key that currently contains {authority} to use {requiredAuthority} so all related strings are standardized (look for the JSON entry that contains the "{authority}" placeholder and replace it with "{requiredAuthority}" to match keys like "active_key_required_message" and "authorization_required_message").
🧹 Nitpick comments (1)
src/config/locales/fil-PH.json (1)
684-686: Unify authority placeholder naming across auth strings.Related auth messages use both
{requiredAuthority}and{authority}. Standardizing to one token reduces interpolation mismatches and translator confusion.Also applies to: 1422-1422
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/fil-PH.json` around lines 684 - 686, Several auth localization entries use both {requiredAuthority} and {authority}; unify them by replacing {requiredAuthority} with {authority} in the affected message keys (e.g., active_key_required_message and authorization_required_message) and any other occurrences (noted at the other occurrence) so all auth strings use the same placeholder token; update the translations to use {authority} consistently to avoid interpolation mismatches.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Major comments:
In `@src/config/locales/ac-ace.json`:
- Around line 612-621: This locale file was edited directly but non-`en-US`
locales must not be changed manually; revert the manual additions/edits for keys
like "operation_failed_with_reason", "wallet_refresh_failed",
"wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", "remove_withdraw_route_failed",
"update_tokens_failed", "swap_failed", "market_data_load_failed" (and the other
ranges called out) back to the Crowdin-synced state, and instead make any new or
updated keys/translations in the canonical en-US.json so they will propagate via
the Crowdin workflow.
In `@src/config/locales/as-IN.json`:
- Around line 612-621: Revert the manual edits to src/config/locales/as-IN.json
(the added/modified keys such as "operation_failed_with_reason",
"wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed",
"boost_failed_with_reason", "add_withdraw_route_failed",
"remove_withdraw_route_failed", "update_tokens_failed", "swap_failed",
"market_data_load_failed" and the other ranges noted) so this locale file is
identical to the repository state before this PR; instead make the intended key
changes only in src/config/locales/en-US.json and let Crowdin sync propagate
translations to as-IN and other locales automatically.
In `@src/config/locales/az-AZ.json`:
- Around line 612-621: This AZ locale file was edited directly but should not be
changed manually; revert the manual modifications to restore crowdin-synced
content and remove the added/modified keys here (e.g.,
"operation_failed_with_reason", "wallet_refresh_failed",
"wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", "remove_withdraw_route_failed",
"update_tokens_failed", "swap_failed", "market_data_load_failed" and the other
ranges noted) and instead make any source key additions/updates only in the
source locale (en-US.json) so Crowdin can propagate translations.
In `@src/config/locales/bg-BG.json`:
- Around line 612-621: Revert all manual edits in src/config/locales/bg-BG.json
(e.g., keys like "operation_failed_with_reason", "wallet_refresh_failed",
"boost_failed", "add_withdraw_route_failed", "update_tokens_failed",
"swap_failed", "market_data_load_failed" and the other ranges called out) back
to the repository's upstream copy; do not keep any translation key changes in
this file—make changes only in en-US and allow Crowdin to propagate translations
to bg-BG. Ensure the bg-BG file matches the last synced state (undo local
modifications introduced by this PR) and remove any manual translations so
localization remains managed by Crowdin.
In `@src/config/locales/bn-BD.json`:
- Around line 612-621: The PR directly modifies localization keys in
src/config/locales/bn-BD.json (e.g., keys like "operation_failed_with_reason",
"wallet_refresh_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", etc.) which breaks the localization flow; instead,
add or update these keys only in en-US.json (the source of truth) and let
Crowdin propagate them to bn-BD and other locales—undo the direct edits to
bn-BD.json, add the new/updated keys to en-US.json, and trigger/schedule the
Crowdin sync so translations are updated automatically.
In `@src/config/locales/bo-BT.json`:
- Around line 612-621: Remove the manually added translation keys (e.g.,
"operation_failed_with_reason", "wallet_refresh_failed",
"wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", "remove_withdraw_route_failed",
"update_tokens_failed", "swap_failed", "market_data_load_failed" and the other
keys mentioned) from this non-en-US locale file and instead add these keys and
English strings to src/config/locales/en-US.json so they are introduced in the
canonical source; do not commit manual edits to bo-BT.json (or other non-en-US
JSONs) — let Crowdin sync propagate translations to other locales.
In `@src/config/locales/bs-BA.json`:
- Around line 612-621: The new translation keys were added directly to
src/config/locales/bs-BA.json but locale changes must be made in
src/config/locales/en-US.json and then synced via Crowdin; remove the manual
additions from bs-BA.json (e.g., keys like "operation_failed_with_reason",
"wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed",
"boost_failed_with_reason", "add_withdraw_route_failed",
"remove_withdraw_route_failed", "update_tokens_failed", "swap_failed",
"market_data_load_failed" and the other ranges mentioned) and instead add or
update those keys only in en-US.json so the Crowdin pipeline can propagate them
to other locale files.
In `@src/config/locales/ca-ES.json`:
- Around line 612-621: Revert the direct additions in
src/config/locales/ca-ES.json (the keys "operation_failed_with_reason",
"wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed",
"boost_failed_with_reason", "add_withdraw_route_failed",
"remove_withdraw_route_failed", "update_tokens_failed", "swap_failed",
"market_data_load_failed" and the other ranges noted) and instead add or update
those keys only in src/config/locales/en-US.json so Crowdin can propagate
translations; specifically, remove the new key entries from the ca-ES.json diff
ranges and add the same key names with English values to en-US.json (or update
existing entries there), then commit the en-US.json change and leave
localization syncing to Crowdin.
In `@src/config/locales/cs-CZ.json`:
- Around line 612-621: Remove the newly added localization keys (e.g.,
"operation_failed_with_reason", "wallet_refresh_failed",
"wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", "remove_withdraw_route_failed",
"update_tokens_failed", "swap_failed", "market_data_load_failed" and the other
keys mentioned) from cs-CZ.json and add or update those keys only inside
src/config/locales/en-US.json so Crowdin can propagate them; ensure you only
modify en-US.json for new/changed keys and leave non-source locale files
(cs-CZ.json) unchanged.
In `@src/config/locales/es-MX.json`:
- Around line 612-621: Revert all manual edits in src/config/locales/es-MX.json
(the newly added/changed keys like "operation_failed_with_reason",
"wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed",
"boost_failed_with_reason", "add_withdraw_route_failed",
"remove_withdraw_route_failed", "update_tokens_failed", "swap_failed",
"market_data_load_failed" and the other ranges noted) back to the state from the
branch’s upstream locale snapshot; instead make any key additions or updates in
src/config/locales/en-US.json only, then let Crowdin propagate translations to
es-MX.json and other locales automatically. Ensure no other non-en-US JSON files
are changed in this PR before pushing the revert.
In `@src/config/locales/et-EE.json`:
- Around line 612-621: The et-EE locale file was modified directly; revert any
manual edits to src/config/locales/et-EE.json (including keys like
"operation_failed_with_reason", "wallet_refresh_failed",
"wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", "remove_withdraw_route_failed",
"update_tokens_failed", "swap_failed", "market_data_load_failed" and the other
ranges noted) and instead add or update those keys only in
src/config/locales/en-US.json; then let the Crowdin sync propagate translations
to other locale files (run your normal Crowdin sync/process after updating
en-US.json).
In `@src/config/locales/fa-IR.json`:
- Around line 612-621: This PR contains manual edits to a non-en-US locale
(fa-IR.json) — revert the changes in this file for the translation keys shown
(e.g., "operation_failed_with_reason", "wallet_refresh_failed",
"wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", "remove_withdraw_route_failed",
"update_tokens_failed", "swap_failed", "market_data_load_failed") and any other
manual edits to non-en-US locale files; ensure only
src/config/locales/en-US.json contains key additions/updates in this PR and let
Crowdin handle synchronization of fa-IR and other locales automatically.
In `@src/config/locales/ga-IE.json`:
- Around line 612-621: This PR includes direct edits to the non-en-US locale
file src/config/locales/ga-IE.json (e.g., keys like
"operation_failed_with_reason", "wallet_refresh_failed",
"boost_failed_with_reason", etc.); remove those changes from the PR and revert
this file to its previous state so only en-US.json is edited and translations
are propagated via Crowdin sync after updating src/config/locales/en-US.json
instead; ensure any added/updated keys are present in en-US.json and drop all
modifications to ga-IE.json (and the other non-en-US ranges mentioned).
In `@src/config/locales/gl-ES.json`:
- Around line 612-621: Revert the manual additions in
src/config/locales/gl-ES.json by removing the new translation keys (e.g.,
"operation_failed_with_reason", "wallet_refresh_failed",
"wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", "remove_withdraw_route_failed",
"update_tokens_failed", "swap_failed", "market_data_load_failed" and the other
ranges noted) so that gl-ES.json remains unchanged in this PR; ensure the new
keys are present only in src/config/locales/en-US.json and let Crowdin handle
propagation to other locales.
In `@src/config/locales/got-DE.json`:
- Around line 612-621: The DE locale file was manually edited—revert any changes
in src/config/locales/got-DE.json for the keys shown (e.g.,
"operation_failed_with_reason", "wallet_refresh_failed",
"wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", "remove_withdraw_route_failed",
"update_tokens_failed", "swap_failed", "market_data_load_failed") and any other
manual edits referenced (around the other ranges mentioned); ensure all new or
updated translation keys are only added to src/config/locales/en-US.json so
Crowdin can synchronize translations for got-DE.json automatically.
In `@src/config/locales/hi-IN.json`:
- Around line 612-621: Revert all manual edits to the hi-IN locale file (remove
the newly added/modified keys such as "operation_failed_with_reason",
"wallet_refresh_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", etc.) so that hi-IN.json matches the repository
state before this PR, and leave the new/updated translation keys only in
en-US.json for Crowdin to sync; ensure hi-IN.json is excluded from manual
changes in the PR (restore the file from git/branch or discard local changes)
and do not add locale keys directly to non-en-US files going forward.
In `@src/config/locales/hy-AM.json`:
- Around line 612-621: Revert the added translation keys in the Armenian locale
file (hy-AM.json) back to its original state and remove the entries for
operation_failed_with_reason, wallet_refresh_failed,
wallet_refresh_missing_account, boost_failed, boost_failed_with_reason,
add_withdraw_route_failed, remove_withdraw_route_failed, update_tokens_failed,
swap_failed, and market_data_load_failed; instead add or update those keys in
the en-US.json master locale (so changes are made only in en-US.json) and then
let the Crowdin sync propagate them to other locales — do not modify any
non-en-US locale files directly.
In `@src/config/locales/is-IS.json`:
- Around line 612-621: Revert the manual edits made to the Icelandic locale by
removing the added/modified translation keys (e.g.,
"operation_failed_with_reason", "wallet_refresh_failed",
"wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", "remove_withdraw_route_failed",
"update_tokens_failed", "swap_failed", "market_data_load_failed" and the other
ranges noted) from the is-IS locale file and restore its previous committed
state; keep any intended source-key updates only in the en-US locale file so
Crowdin can propagate translations to other locales.
In `@src/config/locales/it-IT.json`:
- Around line 612-621: The it-IT locale file contains manual translation-key
edits that should be removed; revert all manual changes in
src/config/locales/it-IT.json (e.g., keys like "operation_failed_with_reason",
"wallet_refresh_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", etc.) back to the Crowdin-synced state and instead
make any new or modified keys in src/config/locales/en-US.json only; ensure you
drop direct edits from it-IT.json (and the other non-source locales noted) so
Crowdin will propagate translations from en-US.json.
In `@src/config/locales/ka-GE.json`:
- Around line 612-621: This file was manually edited but non-en-US locale files
are synced from Crowdin; revert any manual changes here (remove or undo edits to
keys like "operation_failed_with_reason", "wallet_refresh_failed",
"boost_failed_with_reason", "market_data_load_failed", etc.) and instead make
your additions/updates in the canonical en-US.json (add or change the same keys
there). Leave non-en-US JSON files untouched so Crowdin can propagate
translations; if needed, revert this file to the repository version and ensure
future locale key edits are made only in en-US.json.
In `@src/config/locales/kab-KAB.json`:
- Around line 612-621: Revert the manual additions in this locale file and
remove the newly added keys (e.g., "operation_failed_with_reason",
"wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed",
"boost_failed_with_reason", "add_withdraw_route_failed",
"remove_withdraw_route_failed", "update_tokens_failed", "swap_failed",
"market_data_load_failed" and the other mentioned ranges) so that only the en-US
source file contains these changes; leave non-en-US locale files untouched and
rely on Crowdin to propagate translations from en-US.json.
In `@src/config/locales/kk-KZ.json`:
- Around line 612-621: Revert the manual edits made to the non-source locale
file by removing the changes to the kk-KZ locale from this PR (unstage/revert
the file) and ensure any new/updated translation keys are only added to the
canonical en-US locale; specifically undo additions like
"operation_failed_with_reason", "wallet_refresh_failed", "boost_failed",
"boost_failed_with_reason", "add_withdraw_route_failed",
"remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", and
"market_data_load_failed" in the kk-KZ file and keep those key edits only in
en-US.json; also revert the other manual edits mentioned (around the other key
groups referenced in the review) so non-en-US locale files remain untouched and
rely on Crowdin synchronization.
In `@src/config/locales/ko-KR.json`:
- Around line 612-621: This PR contains manual edits to localized keys in
ko-KR.json (e.g., "operation_failed_with_reason", "wallet_refresh_failed",
"wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", "remove_withdraw_route_failed",
"update_tokens_failed", "swap_failed", "market_data_load_failed"): revert those
direct changes in src/config/locales/ko-KR.json so the file remains untouched by
hand, and instead apply any intended key additions/edits only to the source
en-US.json; ensure no other manual edits remain in the other mentioned ko-KR
ranges (lines around 683-688, 1402-1405, 1420-1431) before committing so Crowdin
handles downstream synchronization.
In `@src/config/locales/ku-TR.json`:
- Around line 612-621: Do not modify the non-English locale file entries shown
(keys like "operation_failed_with_reason", "wallet_refresh_failed",
"wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", "remove_withdraw_route_failed",
"update_tokens_failed", "swap_failed", "market_data_load_failed"); instead add
or update these exact keys and their English strings in the en-US locale file
(src/config/locales/en-US.json) so Crowdin can propagate changes to ku-TR.json
automatically; remove any edits made to ku-TR.json in this PR and make the
equivalent additions/updates only in en-US.json.
In `@src/config/locales/ky-KG.json`:
- Around line 612-621: Revert the manual additions in the ky-KG locale file
(remove the newly added keys such as "operation_failed_with_reason",
"wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed",
"boost_failed_with_reason", "add_withdraw_route_failed",
"remove_withdraw_route_failed", "update_tokens_failed", "swap_failed",
"market_data_load_failed" and any other keys added in the ranges mentioned) so
ky-KG returns to its previous state; instead, make these translation key
additions only in en-US.json and let Crowdin propagate them to other locales.
Ensure no other locale files are changed manually in this PR and revert the
similar additions referenced at the other ranges (683-688, 1402-1405,
1420-1431).
In `@src/config/locales/ne-NP.json`:
- Around line 612-621: This PR includes manual translations in the Nepali locale
for keys like "operation_failed_with_reason", "wallet_refresh_failed",
"wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", "remove_withdraw_route_failed",
"update_tokens_failed", "swap_failed", and "market_data_load_failed"; remove
these manual edits from the ne-NP locale file (revert the changes in that file)
so only the en-US.json contains the new/updated keys and let Crowdin propagate
translations to other locales automatically; ensure any other manual additions
mentioned in the review (the other key groups flagged) are likewise reverted
from non-en-US locale files before merging.
In `@src/config/locales/no-NO.json`:
- Around line 612-621: Revert the direct additions/edits made in
src/config/locales/no-NO.json (remove the added keys such as
"operation_failed_with_reason", "wallet_refresh_failed",
"wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", "remove_withdraw_route_failed",
"update_tokens_failed", "swap_failed", "market_data_load_failed" and any other
hunks referenced) and instead add or modify those keys only in
src/config/locales/en-US.json; leave other locale files untouched and rely on
the Crowdin sync to propagate translations. Ensure no manual edits remain in
no-NO.json (undo the diff hunks around the reported lines) and commit changes
only to en-US.json so the repo follows the Crowdin workflow.
In `@src/config/locales/pa-IN.json`:
- Around line 612-621: You added new translation keys (e.g.,
"operation_failed_with_reason", "wallet_refresh_failed",
"wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", "remove_withdraw_route_failed",
"update_tokens_failed", "swap_failed", "market_data_load_failed") directly into
src/config/locales/pa-IN.json; instead, move these additions into the canonical
locale file en-US.json (add the same keys and English strings there) and then
let the Crowdin sync propagate them to pa-IN.json and other locales to avoid
translation drift. Update en-US.json with the new keys/values, remove the direct
edits from pa-IN.json, and run the project's i18n sync process (or mention to
the localization owner) so the translations are distributed correctly.
In `@src/config/locales/ro-RO.json`:
- Around line 612-621: Remove the manual ro-RO locale changes in this PR and
add/update the corresponding keys in en-US.json instead so Crowdin can propagate
translations; specifically delete the added/edited keys like
"operation_failed_with_reason", "wallet_refresh_failed",
"wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", "remove_withdraw_route_failed",
"update_tokens_failed", "swap_failed", and "market_data_load_failed" from
src/config/locales/ro-RO.json (and the other ranges you noted: 683-688,
1402-1405, 1419-1431) and make any intended key changes only in en-US.json so
the Crowdin sync will update other locale files automatically.
In `@src/config/locales/sa-IN.json`:
- Around line 612-621: This file src/config/locales/sa-IN.json was edited
manually; revert the added keys (e.g., "operation_failed_with_reason",
"wallet_refresh_failed", "boost_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", "remove_withdraw_route_failed",
"update_tokens_failed", "swap_failed", "market_data_load_failed" and the other
ranges called out) back to the state in the main branch, and instead add these
translation keys only to src/config/locales/en-US.json (create or update the
keys there); after committing en-US.json changes, rely on Crowdin to propagate
translations to sa-IN.json and other locale files rather than editing them
directly.
In `@src/config/locales/sk-SK.json`:
- Around line 612-621: The new localization keys (e.g.,
"operation_failed_with_reason", "wallet_refresh_failed",
"boost_failed_with_reason", "add_withdraw_route_failed", etc.) were added
directly to src/config/locales/sk-SK.json but non-en-US locale files are
crowdin-managed; revert the changes in sk-SK.json (remove the newly added keys)
and instead add or update these keys only in src/config/locales/en-US.json
(ensure the same key names are present there). Also remove similar direct edits
at the other referenced ranges (lines around 683-688, 1402-1405, 1419-1431) so
all non-en-US files remain unchanged and translations sync correctly via
Crowdin.
In `@src/config/locales/sl-SI.json`:
- Around line 612-621: Revert all direct edits in src/config/locales/sl-SI.json
(remove the added/modified keys such as "operation_failed_with_reason",
"wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed",
"boost_failed_with_reason", "add_withdraw_route_failed",
"remove_withdraw_route_failed", "update_tokens_failed", "swap_failed",
"market_data_load_failed" and any other changed entries noted at ranges 683-688,
1402-1405, 1420-1431) so the file remains unchanged in this PR, and instead add
or update those keys only in src/config/locales/en-US.json per repo workflow so
Crowdin will propagate translations. Ensure no other locale files are modified
in this commit.
In `@src/config/locales/sq-AL.json`:
- Around line 612-621: Do not edit src/config/locales/sq-AL.json directly;
instead add the new/updated translation keys (e.g.
"operation_failed_with_reason", "wallet_refresh_failed",
"wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", "remove_withdraw_route_failed",
"update_tokens_failed", "swap_failed", "market_data_load_failed" and the other
ranges mentioned) into src/config/locales/en-US.json as the source-of-truth,
then trigger the normal Crowdin synchronization (or the repo's i18n sync
workflow) so the sq-AL and other locale files are updated automatically;
revert/remove the direct edits from sq-AL.json to avoid drift.
In `@src/config/locales/sr-CS.json`:
- Around line 612-621: Revert the new translation key additions in
src/config/locales/sr-CS.json (keys such as "operation_failed_with_reason",
"wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed",
"boost_failed_with_reason", "add_withdraw_route_failed",
"remove_withdraw_route_failed", "update_tokens_failed", "swap_failed",
"market_data_load_failed") so that sr-CS.json remains untouched; instead add or
update those translation keys in src/config/locales/en-US.json only (so Crowdin
can propagate them automatically), and remove the sr-CS changes from the
commit/PR.
In `@src/config/locales/sv-SE.json`:
- Around line 612-621: Revert the added/updated translation keys from the
Swedish locale and instead add them only to the English master locale: remove
the entries "operation_failed_with_reason", "wallet_refresh_failed",
"wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", "remove_withdraw_route_failed",
"update_tokens_failed", "swap_failed", and "market_data_load_failed" from the
sv-SE.json changeset, then add those keys (with their English strings) to
en-US.json and submit that change so Crowdin sync can propagate them to sv-SE
and other locales; if you cannot run Crowdin, flag the change for the
localization team to import so translations stay in sync.
In `@src/config/locales/sw-KE.json`:
- Around line 612-621: The new translation keys (e.g.,
"operation_failed_with_reason", "wallet_refresh_failed",
"boost_failed_with_reason", "add_withdraw_route_failed", etc.) were added
directly to sw-KE.json; instead, add or update these keys in the source locale
file en-US.json and remove them from sw-KE.json so Crowdin can propagate
translations. Open src/config/locales/en-US.json, add the same key/value entries
(using the English strings), commit that change, then revert/remove the
corresponding additions from src/config/locales/sw-KE.json so only en-US.json
contains the new keys.
In `@src/config/locales/tg-TJ.json`:
- Around line 612-621: These keys (e.g., "operation_failed_with_reason",
"wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed",
"boost_failed_with_reason", "add_withdraw_route_failed",
"remove_withdraw_route_failed", "update_tokens_failed", "swap_failed",
"market_data_load_failed" and the other keys mentioned in the comment) were
incorrectly added to src/config/locales/tg-TJ.json; revert those edits in
tg-TJ.json and instead add or update the same keys and strings in
src/config/locales/en-US.json (so the canonical locale contains the changes and
Crowdin will sync them), then ensure tg-TJ.json is returned to its original
state in this PR.
In `@src/config/locales/tk-TM.json`:
- Around line 612-621: This locale file was edited directly with new translation
keys (e.g., "operation_failed_with_reason", "wallet_refresh_failed",
"wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", "remove_withdraw_route_failed",
"update_tokens_failed", "swap_failed", "market_data_load_failed" and the other
keys noted around lines 683-688, 1402-1405, 1419-1431); revert all changes in
src/config/locales/tk-TM.json back to the previous committed state, then add
those new keys only to src/config/locales/en-US.json (ensuring identical key
names and message strings) so Crowdin can propagate them to other locales
automatically.
In `@src/config/locales/tr-TR.json`:
- Around line 612-621: You added/updated translation keys directly in tr-TR.json
(e.g., operation_failed_with_reason, wallet_refresh_failed,
wallet_refresh_missing_account, boost_failed, boost_failed_with_reason,
add_withdraw_route_failed, remove_withdraw_route_failed, update_tokens_failed,
swap_failed, market_data_load_failed and other nearby keys), but this file is
Crowdin-synced — revert any manual edits in tr-TR.json and instead add or update
those keys and English strings in en-US.json (matching the same key names and
message text/format), commit the en-US.json changes only, and let the Crowdin
sync propagate translations to tr-TR.json and other locales.
In `@src/config/locales/ur-PK.json`:
- Around line 612-621: The ur-PK.json locale file contains manual translations
that should not be edited directly (e.g., keys like
"operation_failed_with_reason", "wallet_refresh_failed",
"boost_failed_with_reason", "add_withdraw_route_failed",
"market_data_load_failed", etc.); revert/remove any manual additions/edits from
this file and instead add or update those keys only in en-US.json so Crowdin can
auto-sync translations, and ensure you also revert any other manual changes in
this locale file (the other manual-change blocks mentioned in the review) before
pushing.
In `@src/config/locales/uz-UZ.json`:
- Around line 612-621: You edited locale entries directly in
src/config/locales/uz-UZ.json (new keys such as "operation_failed_with_reason",
"wallet_refresh_failed", "boost_failed_with_reason",
"add_withdraw_route_failed", etc. between lines ~612 and the other ranges
noted); revert those direct changes in uz-UZ.json back to the repository version
and instead add or update the keys only in src/config/locales/en-US.json so
Crowdin can propagate them, ensuring the same key names (e.g.,
operation_failed_with_reason, wallet_refresh_failed,
wallet_refresh_missing_account, boost_failed, boost_failed_with_reason,
add_withdraw_route_failed, remove_withdraw_route_failed, update_tokens_failed,
swap_failed, market_data_load_failed) are present in en-US.json and removing
your manual edits from all non-en-US locale files listed (including the other
ranges 683-688, 1402-1405, 1419-1431).
In `@src/config/locales/zh-CN.json`:
- Around line 612-621: The PR includes manual edits to Chinese locale keys (e.g.
"operation_failed_with_reason", "wallet_refresh_failed", "boost_failed",
"add_withdraw_route_failed", "remove_withdraw_route_failed",
"update_tokens_failed", "swap_failed", "market_data_load_failed" and the other
ranges mentioned), but zh-CN must not be edited manually; revert all changes in
src/config/locales/zh-CN.json back to the state before this PR and instead add
or update the new/changed keys only in src/config/locales/en-US.json so Crowdin
can propagate translations; ensure the revert removes the manual key
introductions and leave localization sync to the Crowdin workflow.
---
Minor comments:
In `@src/config/locales/hu-HU.json`:
- Around line 684-686: Localization placeholders are inconsistent: some messages
use {requiredAuthority} while another uses {authority}; update the message key
that currently contains {authority} to use {requiredAuthority} so all related
strings are standardized (look for the JSON entry that contains the
"{authority}" placeholder and replace it with "{requiredAuthority}" to match
keys like "active_key_required_message" and "authorization_required_message").
---
Nitpick comments:
In `@src/config/locales/fil-PH.json`:
- Around line 684-686: Several auth localization entries use both
{requiredAuthority} and {authority}; unify them by replacing {requiredAuthority}
with {authority} in the affected message keys (e.g., active_key_required_message
and authorization_required_message) and any other occurrences (noted at the
other occurrence) so all auth strings use the same placeholder token; update the
translations to use {authority} consistently to avoid interpolation mismatches.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: ba7462b3-a313-4c9a-b9d2-459b922ad3f2
📒 Files selected for processing (77)
src/config/locales/ac-ace.jsonsrc/config/locales/ar-SA.jsonsrc/config/locales/as-IN.jsonsrc/config/locales/az-AZ.jsonsrc/config/locales/bg-BG.jsonsrc/config/locales/bn-BD.jsonsrc/config/locales/bo-BT.jsonsrc/config/locales/bs-BA.jsonsrc/config/locales/ca-ES.jsonsrc/config/locales/ceb-PH.jsonsrc/config/locales/cs-CZ.jsonsrc/config/locales/da-DK.jsonsrc/config/locales/de-DE.jsonsrc/config/locales/el-GR.jsonsrc/config/locales/en-US.jsonsrc/config/locales/eo-UY.jsonsrc/config/locales/es-AR.jsonsrc/config/locales/es-ES.jsonsrc/config/locales/es-MX.jsonsrc/config/locales/et-EE.jsonsrc/config/locales/fa-IR.jsonsrc/config/locales/fi-FI.jsonsrc/config/locales/fil-PH.jsonsrc/config/locales/fr-FR.jsonsrc/config/locales/ga-IE.jsonsrc/config/locales/gl-ES.jsonsrc/config/locales/got-DE.jsonsrc/config/locales/he-IL.jsonsrc/config/locales/hi-IN.jsonsrc/config/locales/hr-HR.jsonsrc/config/locales/hu-HU.jsonsrc/config/locales/hy-AM.jsonsrc/config/locales/id-ID.jsonsrc/config/locales/is-IS.jsonsrc/config/locales/it-IT.jsonsrc/config/locales/ja-JP.jsonsrc/config/locales/ka-GE.jsonsrc/config/locales/kab-KAB.jsonsrc/config/locales/kk-KZ.jsonsrc/config/locales/ko-KR.jsonsrc/config/locales/ks-IN.jsonsrc/config/locales/ku-TR.jsonsrc/config/locales/ky-KG.jsonsrc/config/locales/lt-LT.jsonsrc/config/locales/lv-LV.jsonsrc/config/locales/mk-MK.jsonsrc/config/locales/mn-MN.jsonsrc/config/locales/ms-MY.jsonsrc/config/locales/ne-NP.jsonsrc/config/locales/nl-NL.jsonsrc/config/locales/no-NO.jsonsrc/config/locales/pa-IN.jsonsrc/config/locales/pcm-NG.jsonsrc/config/locales/pl-PL.jsonsrc/config/locales/pt-PT.jsonsrc/config/locales/ro-RO.jsonsrc/config/locales/ru-RU.jsonsrc/config/locales/sa-IN.jsonsrc/config/locales/sk-SK.jsonsrc/config/locales/sl-SI.jsonsrc/config/locales/sq-AL.jsonsrc/config/locales/sr-CS.jsonsrc/config/locales/sv-SE.jsonsrc/config/locales/sw-KE.jsonsrc/config/locales/ta-IN.jsonsrc/config/locales/tg-TJ.jsonsrc/config/locales/th-TH.jsonsrc/config/locales/tk-TM.jsonsrc/config/locales/tr-TR.jsonsrc/config/locales/uk-UA.jsonsrc/config/locales/ur-IN.jsonsrc/config/locales/ur-PK.jsonsrc/config/locales/uz-UZ.jsonsrc/config/locales/vi-VN.jsonsrc/config/locales/yo-NG.jsonsrc/config/locales/zh-CN.jsonsrc/config/locales/zh-TW.json
🚧 Files skipped from review as they are similar to previous changes (17)
- src/config/locales/ta-IN.json
- src/config/locales/ar-SA.json
- src/config/locales/pcm-NG.json
- src/config/locales/ru-RU.json
- src/config/locales/zh-TW.json
- src/config/locales/pt-PT.json
- src/config/locales/ks-IN.json
- src/config/locales/id-ID.json
- src/config/locales/ceb-PH.json
- src/config/locales/lt-LT.json
- src/config/locales/uk-UA.json
- src/config/locales/fi-FI.json
- src/config/locales/lv-LV.json
- src/config/locales/da-DK.json
- src/config/locales/ur-IN.json
- src/config/locales/es-ES.json
- src/config/locales/de-DE.json
There was a problem hiding this comment.
Note
Due to the large number of review comments, Critical severity comments were prioritized as inline comments.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
src/config/locales/az-AZ.json (1)
1-1433:⚠️ Potential issue | 🟠 MajorKeep manual i18n key changes scoped to
en-US.jsononly.If this is a manually authored PR, non-
en-USlocale edits should be removed and left to Crowdin sync; otherwise these changes risk being overwritten and create translation drift in review history.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/az-AZ.json` around lines 1 - 1433, The PR contains manual edits to a non-en-US locale (az-AZ.json) which must not be changed directly; revert all manual changes in src/config/locales/az-AZ.json (e.g., entries like "profile.havent_commented", "post_poll.choice_placeholder", and other added/edited keys) and instead make your intended key additions/updates only in en-US.json so Crowdin can propagate them; if you intended to add new keys, copy those changes into the en-US.json master file, commit that change, and remove/revert any edits to az-AZ.json before updating the branch.
🟠 Major comments (40)
src/config/locales/hu-HU.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorPlease avoid direct locale-key edits in
hu-HU.jsonfor this workflow.These additions should be made in
src/config/locales/en-US.jsononly, then propagated via Crowdin sync. Please move the source key updates toen-US.json(or confirm this PR is the automated Crowdin sync output branch).Based on learnings: In the ecency-mobile repository, only the
en-US.jsonlocale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration and should not be manually edited in pull requests.Also applies to: 683-688, 1402-1405, 1420-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/hu-HU.json` around lines 612 - 621, You added new translation keys directly into src/config/locales/hu-HU.json (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "boost_failed", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed"); move these key additions into src/config/locales/en-US.json instead and remove them from hu-HU.json so that Crowdin handles propagation, or if this PR is the automated Crowdin sync branch explicitly confirm that and leave as-is; repeat the same change for the other referenced ranges (lines around 683-688, 1402-1405, 1420-1431) so only en-US.json is the source of truth.src/config/locales/ko-KR.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorNon-
en-USlocale changes should be excluded from this PR.This file includes direct key additions in
ko-KR.json. Per repository localization process, onlysrc/config/locales/en-US.jsonshould be edited; translated locale files are Crowdin-managed.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files (e.g., es-ES.json, de-DE.json, etc.) are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.
Also applies to: 683-688, 1402-1405, 1420-1431
src/config/locales/et-EE.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorKeep locale source-of-truth changes in
en-US.jsononly.Direct edits in
et-EE.jsonshould be avoided if Crowdin is the sync source for non-en-USlocales. Please move key updates tosrc/config/locales/en-US.jsonand rely on localization sync for this file.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files (e.g., es-ES.json, de-DE.json, etc.) are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.
Also applies to: 683-688, 1402-1405, 1420-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/et-EE.json` around lines 612 - 621, Revert the direct edits in et-EE.json for the translation keys shown (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed") and instead add or update those keys only in src/config/locales/en-US.json so Crowdin can sync non-en-US locales; ensure you also remove or revert similar manual changes referenced at the other ranges (683-688, 1402-1405, 1420-1431) and leave et-EE.json unchanged except for Crowdin-managed syncs.src/config/locales/sw-KE.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorAvoid manual edits in non-
en-USlocale files.These additions are in
sw-KE, but this repo’s localization workflow expects key changes only insrc/config/locales/en-US.json; other locales should be synchronized by Crowdin.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files (e.g., es-ES.json, de-DE.json, etc.) are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.
Also applies to: 683-688, 1402-1405, 1420-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/sw-KE.json` around lines 612 - 621, This PR incorrectly adds translation keys directly into non-en-US locale files (e.g., keys "operation_failed_with_reason", "wallet_refresh_failed", "boost_failed_with_reason", "market_data_load_failed" in sw-KE.json); revert those manual edits and instead add or update the keys only in src/config/locales/en-US.json, then let the Crowdin sync propagate translations to other locale files—remove the added entries from sw-KE.json (and the other mentioned locales) so only en-US contains the new/changed keys.src/config/locales/es-ES.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorPlease remove manual edits to
es-ES.jsonfrom this PR.These key additions should originate from
src/config/locales/en-US.jsononly, with Crowdin handling updates for localized files likees-ES.json.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files (e.g., es-ES.json, de-DE.json, etc.) are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.
Also applies to: 683-688, 1402-1405, 1420-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/es-ES.json` around lines 612 - 621, Revert the manual additions in the es-ES.json file (remove the keys operation_failed_with_reason, wallet_refresh_failed, wallet_refresh_missing_account, boost_failed, boost_failed_with_reason, add_withdraw_route_failed, remove_withdraw_route_failed, update_tokens_failed, swap_failed, market_data_load_failed and the other key sets mentioned around lines 683-688, 1402-1405, 1420-1431) so localized files are unchanged in this PR; make any new or updated translation keys only in src/config/locales/en-US.json and let Crowdin propagate them to es-ES.json and other locale files.src/config/locales/zh-TW.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorPlease keep direct locale edits limited to
en-US.json.
zh-TW.jsonis being edited directly here, but this repository’s workflow is to update onlysrc/config/locales/en-US.jsonand let Crowdin propagate updates to localized files.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files (e.g., es-ES.json, de-DE.json, etc.) are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.
Also applies to: 683-688, 1402-1405, 1420-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/zh-TW.json` around lines 612 - 621, You edited translation keys directly in zh-TW.json (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed" and the other key groups noted in the review); revert those direct changes in zh-TW.json and instead add or update the same keys only in src/config/locales/en-US.json so Crowdin can propagate them to localized files, ensuring you remove manual edits from all non-en-US locale files mentioned.src/config/locales/sv-SE.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorPlease remove manual key updates from this Crowdin-managed locale file.
Keep source key changes in
src/config/locales/en-US.jsonand rely on Crowdin sync forsv-SE.json.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files (e.g., es-ES.json, de-DE.json, etc.) are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.
Also applies to: 683-688, 1402-1405, 1420-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/sv-SE.json` around lines 612 - 621, This Crowdin-managed locale file has manual edits to translation keys (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed") and should not be changed here; revert any manual changes in src/config/locales/sv-SE.json back to the synced state and remove all added/modified keys from this file, keeping source edits only in src/config/locales/en-US.json and relying on Crowdin to propagate them (also revert similar manual edits around the other mentioned ranges).src/config/locales/it-IT.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorThis file should not receive manual localization key edits in PRs.
Apply these additions in
src/config/locales/en-US.jsononly and let Crowdin syncit-IT.json.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files (e.g., es-ES.json, de-DE.json, etc.) are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.
Also applies to: 683-688, 1402-1405, 1420-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/it-IT.json` around lines 612 - 621, These new translation keys (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed") were accidentally added directly to src/config/locales/it-IT.json; revert/remove these additions from it-IT.json (and the other locale blocks noted: lines around 683-688, 1402-1405, 1420-1431) and instead add the new keys only to src/config/locales/en-US.json so Crowdin can propagate them to other locales automatically; ensure you keep the exact key names and message strings when adding to en-US.json and push that single-file change.src/config/locales/kk-KZ.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorThis locale file should be excluded from manual translation-key updates.
Please keep these additions in
src/config/locales/en-US.jsononly and let Crowdin propagate the rest.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files (e.g., es-ES.json, de-DE.json, etc.) are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.
Also applies to: 683-688, 1402-1405, 1420-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/kk-KZ.json` around lines 612 - 621, Revert the manual additions in src/config/locales/kk-KZ.json for the listed keys (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed") and any other manual edits referenced in the comment; instead place the new/updated translation keys only into src/config/locales/en-US.json so Crowdin can propagate them to other locales automatically. Ensure the PR does not include changes to non-en-US locale files (including the other ranges noted) and keep only en-US.json as the source-of-truth for these key additions.src/config/locales/sr-CS.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorDo not manually edit this Crowdin-managed locale file.
These key additions should be made only in
src/config/locales/en-US.json; non-English locale files should be synced by Crowdin automation instead of being edited in PRs.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files (e.g., es-ES.json, de-DE.json, etc.) are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.
Also applies to: 683-688, 1402-1405, 1420-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/sr-CS.json` around lines 612 - 621, This Crowdin-managed Serbian locale file was modified directly — revert the changes in src/config/locales/sr-CS.json (remove the added keys such as "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed" and the other ranges mentioned) and instead add any new or updated translation keys only to src/config/locales/en-US.json so the Crowdin pipeline can propagate them to other locales; ensure you remove your edits from sr-CS.json (and the other indicated ranges) from the PR and commit the en-US.json changes only.src/config/locales/no-NO.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorManual changes to this non-
en-USlocale should be reverted.The new keys should be introduced in
src/config/locales/en-US.jsononly; Crowdin should handle synchronization intono-NO.json.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files (e.g., es-ES.json, de-DE.json, etc.) are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.
Also applies to: 683-688, 1402-1405, 1420-1431
src/config/locales/zh-CN.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorDo not manually update non-
en-USlocale files in this PR.These key additions should be introduced in
src/config/locales/en-US.jsononly; Crowdin should propagate them tozh-CN.json. Please revert manual edits in this file.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration.
Also applies to: 683-688, 1402-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/zh-CN.json` around lines 612 - 621, This change manually adds new translation keys (e.g. "operation_failed_with_reason", "wallet_refresh_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed") to src/config/locales/zh-CN.json; revert these edits in zh-CN.json and instead add the new keys only to src/config/locales/en-US.json so Crowdin can propagate them to other locales, and ensure any other manual additions the reviewer flagged (lines around 683-688 and 1402-1431) are similarly reverted from non-en-US locale files.src/config/locales/es-MX.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorDo not add localization keys directly in
es-MX.json.Please keep key additions/changes in
src/config/locales/en-US.jsononly and rely on Crowdin to synchronize this locale.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration.
Also applies to: 683-688, 1402-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/es-MX.json` around lines 612 - 621, This change adds new localization keys directly into src/config/locales/es-MX.json (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed"); instead, remove these additions from es-MX.json and add or update them only in src/config/locales/en-US.json so Crowdin can propagate translations; ensure you undo the edits in es-MX.json (including the other ranges mentioned: 683-688, 1402-1431) and commit only the en-US.json changes.src/config/locales/sk-SK.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 Major
sk-SK.jsonshould not be manually modified for key additions.Move these key changes to
src/config/locales/en-US.jsonand let Crowdin handle propagation into this locale file.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration.
Also applies to: 683-688, 1402-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/sk-SK.json` around lines 612 - 621, The added translation keys (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed" and the other ranges noted) must not be added directly to src/config/locales/sk-SK.json; instead, add or update these keys only in src/config/locales/en-US.json so Crowdin can propagate them to other locales, then revert/remove these manual edits from sk-SK.json; search for the listed key names to locate the changes (and the other ranges 683-688, 1402-1431) and ensure en-US.json contains the new/updated keys while sk-SK.json is restored to its Crowdin-managed state.src/config/locales/as-IN.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorPlease avoid manual key changes in
as-IN.json.Per the repo localization workflow, add/update keys in
src/config/locales/en-US.jsonand let Crowdin sync this locale automatically.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration.
Also applies to: 683-688, 1402-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/as-IN.json` around lines 612 - 621, You manually added/edited translation keys in as-IN.json (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed"); revert those manual edits in src/config/locales/as-IN.json back to its synced state and instead add or update these keys in src/config/locales/en-US.json so Crowdin can propagate them automatically; ensure you only modify en-US.json for new/changed keys and remove any local changes in other affected ranges (noted around lines 683-688 and 1402-1431) before committing.src/config/locales/pa-IN.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorManual updates to
pa-IN.jsonshould be reverted.These new keys belong in
src/config/locales/en-US.json; this locale should be updated by Crowdin sync, not directly in the PR.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration.
Also applies to: 683-688, 1402-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/pa-IN.json` around lines 612 - 621, The pa-IN.json file was manually edited to add new translation keys (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed" and other keys in the ranges you flagged) — revert those manual additions in src/config/locales/pa-IN.json so it matches the Crowdin-synced state, then place any intended new keys only in src/config/locales/en-US.json (or ensure they are added via the Crowdin source) so the localization sync can propagate them to other locales; locate the edits by the key names and the noted ranges (612-621, 683-688, 1402-1431) when reverting and updating.src/config/locales/ks-IN.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorDo not commit locale-key updates directly in
ks-IN.jsonThese changes should be sourced from
src/config/locales/en-US.jsonand synced via Crowdin, not edited manually in this locale file.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files (e.g., es-ES.json, de-DE.json, etc.) are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.
Also applies to: 683-688, 1402-1405, 1420-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/ks-IN.json` around lines 612 - 621, The ks-IN.json file was edited directly to add/update translation keys (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "boost_failed_with_reason", "add_withdraw_route_failed", etc.); revert these manual edits in src/config/locales/ks-IN.json and remove any added/changed keys so the file matches the synchronized Crowdin output, then make the canonical changes in src/config/locales/en-US.json only and allow Crowdin to propagate them to other locales; also revert the manual edits in the other referenced blocks (around the ranges you noted) to avoid committing localized changes directly.src/config/locales/th-TH.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorExclude
th-TH.jsonfrom manual localization editsThese additions should not be committed directly in this locale file. Keep key changes in
src/config/locales/en-US.jsononly and let Crowdin syncth-TH.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files (e.g., es-ES.json, de-DE.json, etc.) are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.
Also applies to: 683-688, 1402-1405, 1420-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/th-TH.json` around lines 612 - 621, Revert the manual additions in th-TH.json (the new keys like "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed" and the other ranges noted) and instead add or update these keys only in en-US.json; leave non-en locale files unchanged so Crowdin can sync translations automatically, and ensure future translation key changes are made in en-US.json only.src/config/locales/cs-CZ.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorDo not manually edit Crowdin-managed locale files
This file is a non-
en-USlocale, but it contains direct key additions. Please remove these changes from the PR and add/update keys only insrc/config/locales/en-US.json; Crowdin should propagate the rest.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files (e.g., es-ES.json, de-DE.json, etc.) are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.
Also applies to: 683-688, 1402-1405, 1420-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/cs-CZ.json` around lines 612 - 621, The PR incorrectly adds/edits translation keys directly in a Crowdin-managed non-en-US locale (src/config/locales/cs-CZ.json) — remove the manual additions for keys like "operation_failed_with_reason", "wallet_refresh_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "market_data_load_failed" (and the other ranges referenced) from this file and instead add or update those keys only in src/config/locales/en-US.json so Crowdin can propagate them; ensure you revert cs-CZ.json to its original state and commit the intended key changes into en-US.json only.src/config/locales/pl-PL.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorManual changes in
pl-PL.jsonshould be revertedThis locale file appears Crowdin-managed. Please remove these edits from the PR and keep localization key additions in
src/config/locales/en-US.jsononly.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files (e.g., es-ES.json, de-DE.json, etc.) are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.
Also applies to: 683-688, 1402-1405, 1420-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/pl-PL.json` around lines 612 - 621, Revert the manual edits in src/config/locales/pl-PL.json and remove the added translation keys/changes (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed") so this file is identical to the Crowdin-managed source; instead add or update these keys only in src/config/locales/en-US.json, and ensure you also revert any other manual changes in the pl-PL.json ranges noted in the review (the other affected ranges) so no non-English locale is modified in the PR.src/config/locales/ro-RO.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorCrowdin sync workflow violation in
ro-RO.jsonPlease drop these manual locale updates from this file and keep the source-of-truth key changes in
src/config/locales/en-US.jsononly.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files (e.g., es-ES.json, de-DE.json, etc.) are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.
Also applies to: 683-688, 1402-1405, 1420-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/ro-RO.json` around lines 612 - 621, This file contains manual translations that must not be edited directly; revert the manual changes for the keys shown ("operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed") and any other manual edits you made in the other flagged ranges, remove these additions from this ro-RO.json, and ensure the source-of-truth changes are made only in en-US.json so Crowdin can propagate them; restore the ro-RO.json entries to the Crowdin-synced state (or discard your local edits) and keep only the en-US.json key changes in the PR.src/config/locales/ac-ace.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorDrop direct edits to this locale file.
Per repository localization flow, key additions/updates should be made in
src/config/locales/en-US.jsononly; this locale should be synchronized via Crowdin, not manually edited here.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.
Also applies to: 683-688, 1402-1405, 1419-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/ac-ace.json` around lines 612 - 621, This file contains manual edits to localized keys (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "boost_failed_with_reason", "add_withdraw_route_failed", etc.) which must not be changed directly; revert these changes in src/config/locales/ac-ace.json and instead apply any additions or modifications to the canonical locale file src/config/locales/en-US.json so Crowdin can propagate them; ensure you remove the manual edits across the other affected ranges (around lines referenced: 683-688, 1402-1405, 1419-1431) and let the localization pipeline synchronize translations rather than committing direct edits to non-en-US locale files.src/config/locales/ku-TR.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorRemove this non-
en-USlocale update from the PR.This file should not be directly updated for key additions; keep key changes in
src/config/locales/en-US.jsonand rely on Crowdin sync for this locale.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.
Also applies to: 683-688, 1402-1405, 1419-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/ku-TR.json` around lines 612 - 621, Revert the manual key additions in src/config/locales/ku-TR.json (remove the keys shown: operation_failed_with_reason, wallet_refresh_failed, wallet_refresh_missing_account, boost_failed, boost_failed_with_reason, add_withdraw_route_failed, remove_withdraw_route_failed, update_tokens_failed, swap_failed, market_data_load_failed and the other manual edits at the ranges referenced) and instead add or update those translation keys only in src/config/locales/en-US.json; keep ku-TR.json untouched so Crowdin can sync translations automatically.src/config/locales/sl-SI.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorPlease exclude this locale file from manual translation-key updates.
These additions should originate in
src/config/locales/en-US.json, with locale propagation handled by Crowdin sync.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.
Also applies to: 683-688, 1402-1405, 1419-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/sl-SI.json` around lines 612 - 621, This PR manually modified locale keys in sl-SI (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed" and the other ranges noted); revert these changes in src/config/locales/sl-SI.json so it matches the Crowdin-managed state, and instead add or update the new/changed keys only in src/config/locales/en-US.json; do not manually edit other locale files (including the other key ranges 683-688, 1402-1405, 1419-1431) because Crowdin will propagate translations.src/config/locales/fr-FR.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorRemove direct edits to this non-
en-USlocale file.For key additions/updates, this repository expects changes in
src/config/locales/en-US.jsononly; this file should be Crowdinsynced, not manually changed in this PR.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.
Also applies to: 683-688, 1402-1405, 1419-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/fr-FR.json` around lines 612 - 621, Revert any manual edits in src/config/locales/fr-FR.json (specifically remove the added/updated keys like "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed" and the other ranges noted) and instead make the key additions/changes only in src/config/locales/en-US.json; Crowdin will propagate translations to fr-FR.json, so ensure en-US.json contains the new/updated keys and remove the manual changes from non-en-US locale files before committing.src/config/locales/ar-SA.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorThis locale file should not be part of manual key-update changes.
Please remove these changes from this file and keep key updates in
src/config/locales/en-US.json; Crowdin should propagate locale updates.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.
Also applies to: 683-688, 1402-1405, 1419-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/ar-SA.json` around lines 612 - 621, Revert the manual changes in src/config/locales/ar-SA.json: remove the newly added/modified translation keys (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed" and the other ranges noted) so ar-SA.json remains unchanged; instead make your key additions/edits only in src/config/locales/en-US.json and let Crowdin propagate them to other locale files—ensure no manual edits remain in non-en-US locale files before committing.src/config/locales/vi-VN.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorPlease remove manual changes from
vi-VN.json.Keep localization key changes in
src/config/locales/en-US.jsonand rely on Crowdin synchronization for this locale.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.
Also applies to: 683-688, 1402-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/vi-VN.json` around lines 612 - 621, This commit added manual translation changes to vi-VN.json (e.g., keys like "operation_failed_with_reason", "wallet_refresh_failed", "boost_failed_with_reason", "add_withdraw_route_failed", etc.); revert those manual edits and restore vi-VN.json to its Crowdin-synced state so only en-US.json contains the source-of-truth key changes, and ensure future key additions/edits are made in src/config/locales/en-US.json (also remove the other manual changes noted around the ranges 683-688 and 1402-1431).src/config/locales/ceb-PH.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorAvoid direct edits to
ceb-PH.jsonin feature PRs.These updates should originate from
en-US.jsonand be propagated via Crowdin sync, not committed directly here.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.
Also applies to: 683-688, 1402-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/ceb-PH.json` around lines 612 - 621, This change illegally edits the ceb-PH locale file directly; revert the edits to keys like "operation_failed_with_reason", "wallet_refresh_failed", "boost_failed_with_reason", etc., and instead apply your additions/updates to en-US.json (the source of truth) so they can be propagated via Crowdin; after reverting ceb-PH.json, update en-US.json with the new/changed keys and trigger the repository’s Crowdin sync process (or follow the project’s localization workflow) to propagate translations to ceb-PH and other locales.src/config/locales/ms-MY.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorThis locale file should not be manually updated in this PR.
Please revert
ms-MY.jsonchanges and keep the source key updates insrc/config/locales/en-US.jsononly.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.
Also applies to: 683-688, 1402-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/ms-MY.json` around lines 612 - 621, Revert all manual changes made to the ms-MY.json locale (remove any added/modified keys such as "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed" and any other keys you changed) so that only the source en-US.json contains the new/updated translation keys; ensure no other locale files are modified in this PR and leave localization sync to the Crowdin pipeline.src/config/locales/fi-FI.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorPlease exclude
fi-FI.jsonfrom manual localization changes.Per project workflow, add/update keys in
en-US.jsononly and let Crowdin update this locale file automatically.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.
Also applies to: 683-688, 1402-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/fi-FI.json` around lines 612 - 621, The commit incorrectly edits src/config/locales/fi-FI.json; per project workflow you must not manually change localized files—revert any edits to fi-FI.json (including keys like "operation_failed_with_reason", "wallet_refresh_failed", "boost_failed_with_reason", "add_withdraw_route_failed", etc.) and instead add or update these keys in src/config/locales/en-US.json so Crowdin can propagate them; ensure no other locale files are modified (also revert changes around the other ranges noted) before pushing.src/config/locales/mk-MK.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorRevert direct edits to this non-
en-USlocale file.These key additions should be removed from this file and introduced only in
src/config/locales/en-US.json; Crowdin sync should propagate them tomk-MK.json.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.
Also applies to: 683-688, 1402-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/mk-MK.json` around lines 612 - 621, Revert the manual additions in the mk-MK locale file: remove the newly added translation keys (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed" and the other key blocks called out) from mk-MK.json and instead add these keys only to en-US.json so Crowdin can propagate them; ensure no other non-en-US locale files are directly edited in this PR and leave mk-MK.json identical to the Crowdin-synced state.src/config/locales/yo-NG.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorNon-
en-USlocale updates should not be committed directly.Please revert manual changes in this file and let Crowdin propagate these keys.
Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration.
Also applies to: 683-688, 1402-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/yo-NG.json` around lines 612 - 621, This file contains manually added/edited translation keys (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed"); revert these manual changes in src/config/locales/yo-NG.json and restore the previous version so non-en-US locales remain managed by Crowdin, and instead apply any new or changed keys only to en-US.json so Crowdin can propagate them to other locale files.src/config/locales/hy-AM.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorThis locale file should not be manually modified in PRs.
These additions need to come from Crowdin sync, not direct edits in
hy-AM.json.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration.
Also applies to: 683-688, 1402-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/hy-AM.json` around lines 612 - 621, This PR directly modifies locale keys (e.g. "operation_failed_with_reason", "wallet_refresh_failed", "boost_failed_with_reason", "add_withdraw_route_failed", etc.) in hy-AM.json which is forbidden; revert the manual edits to hy-AM.json (and the other noted sections around the 683-688 and 1402-1431 ranges) and instead add or update the keys in en-US.json so the Crowdin sync will propagate them to hy-AM and other locales automatically; ensure no other non-en-US locale files are changed in this PR.src/config/locales/de-DE.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorPlease remove manual locale-key edits from
de-DE.json.This should be synchronized by Crowdin after
en-US.jsonupdates, not edited directly in the PR.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration.
Also applies to: 683-688, 1402-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/de-DE.json` around lines 612 - 621, Revert manual edits to the German locale file by removing the added/changed keys (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed" and the other ranges mentioned) so de-DE.json is left untouched; instead make the canonical changes in en-US.json only and let Crowdin synchronize translations automatically—ensure no direct locale-key edits remain in de-DE.json before committing.src/config/locales/ur-IN.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorDo not manually edit non-
en-USlocale files in this repository.This file should be excluded from manual translation-key updates and left to Crowdin synchronization.
Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration.
Also applies to: 683-688, 1402-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/ur-IN.json` around lines 612 - 621, This file is a non-en-US locale and should not be edited directly; revert any manual changes to keys such as "operation_failed_with_reason", "wallet_refresh_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed" (and the other keys noted in the comment) and instead make your translation-key additions/updates in the canonical en-US locale file so Crowdin can synchronize them to other locales; ensure the en-US.json contains the new/updated keys and leave this ur-IN.json to be updated only by Crowdin.src/config/locales/lt-LT.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorRevert direct key additions in
lt-LT.json.These updates should be made in
src/config/locales/en-US.jsononly; localized files are expected to be synchronized automatically via Crowdin.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration.
Also applies to: 683-688, 1402-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/lt-LT.json` around lines 612 - 621, Revert the direct additions of translation keys in lt-LT.json (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed") and remove the similar direct edits in the other flagged ranges (lines around 683-688 and 1402-1431); instead add or update these keys only in en-US.json so Crowdin will propagate them to localized files automatically. Ensure you delete the newly added key entries from lt-LT.json and commit the authoritative additions to en-US.json (using the same key names and message strings) so the translation sync remains consistent.src/config/locales/uk-UA.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorRemove manual updates from non-
en-USlocale files in this PR.This file should not be manually edited for new/updated keys. Please keep these additions in
src/config/locales/en-US.jsononly and let Crowdin sync propagate them touk-UA.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration.
Also applies to: 683-688, 1402-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/uk-UA.json` around lines 612 - 621, This PR added new/updated translation keys directly into uk-UA.json (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed"); revert those manual edits in src/config/locales/uk-UA.json so it matches the upstream Crowdin-managed state, ensure the new keys exist only in src/config/locales/en-US.json (or add them there if missing), and rely on the Crowdin sync to propagate them to uk-UA rather than committing localized files here.src/config/locales/sq-AL.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorPlease drop manual locale-key changes from
sq-AL.json.Per repo workflow, these key additions should be authored in
src/config/locales/en-US.jsononly; non-base locales are synchronized via Crowdin.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration.
Also applies to: 683-688, 1402-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/sq-AL.json` around lines 612 - 621, Remove the manually added translation keys from src/config/locales/sq-AL.json (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed" and the other ranges mentioned) and instead add those keys only to the base locale file src/config/locales/en-US.json with their English strings; Crowdin will propagate them to non-base locales, so do not keep manual edits in sq-AL.json.src/config/locales/bn-BD.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 MajorDo not manually edit
bn-BD.jsonfor new translation keys in this repository workflow.Please move/keep these key additions in
src/config/locales/en-US.jsonand remove the non-en-USmanual changes from this PR.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration.
Also applies to: 683-688, 1402-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/bn-BD.json` around lines 612 - 621, The bn-BD.json file has manual additions for translation keys (e.g., "operation_failed_with_reason", "wallet_refresh_failed", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed" and others in ranges 683-688 and 1402-1431); revert/remove these non-en-US changes from src/config/locales/bn-BD.json and instead add or update the canonical keys in src/config/locales/en-US.json (ensure you add the exact key names and default English strings), then commit the change so Crowdin can sync translations automatically.src/config/locales/nl-NL.json-612-621 (1)
612-621:⚠️ Potential issue | 🟠 Major
nl-NL.jsonshould not be manually updated in this change set.Please keep these localization key additions in
src/config/locales/en-US.jsononly and remove this file’s manual updates from the PR.Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration.
Also applies to: 683-688, 1402-1431
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/nl-NL.json` around lines 612 - 621, Revert the manual localization key additions in nl-NL.json by removing the added keys (e.g. "operation_failed_with_reason", "wallet_refresh_failed", "wallet_refresh_missing_account", "boost_failed", "boost_failed_with_reason", "add_withdraw_route_failed", "remove_withdraw_route_failed", "update_tokens_failed", "swap_failed", "market_data_load_failed") so that nl-NL.json is not changed in this PR; ensure the new/updated keys remain only in en-US.json and do not manually modify other locale files (any other manual key additions in the same commit ranges should be removed as well).
🟡 Minor comments (1)
src/config/locales/en-US.json-1422-1422 (1)
1422-1422:⚠️ Potential issue | 🟡 MinorAlign placeholder naming to avoid interpolation misses.
Line 1422 uses
{authority}while related auth strings use{requiredAuthority}(Lines 684 and 686). Keep one placeholder name across keys.🔧 Proposed fix
- "description": "This operation requires {authority} authority. Choose how to sign:", + "description": "This operation requires {requiredAuthority} authority. Choose how to sign:",🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/config/locales/en-US.json` at line 1422, The locale string uses the placeholder {authority} which is inconsistent with other auth messages that use {requiredAuthority}; update the description value in en-US.json to use {requiredAuthority} instead of {authority} so interpolation matches the other auth strings (i.e., replace "{authority}" with "{requiredAuthority}" in the affected "description" entry).
|
@CodeRabbit going forward never review any PR with l10n_development branch |
|
Tip For best results, initiate chat on the files or code changes. 🧩 Analysis chain
You can also make this permanent by configuring CodeRabbit to ignore this branch in your reviews:
auto_review:
ignore_title_keywords:
- "New Crowdin"Or more precisely, to filter by the source branch, you can use path-based or branch filtering. I'd recommend fetching the latest config schema to confirm the exact option — let me pull that up for you. 🛠 Debug Information Gathered
To make this permanent and automatic, the schema doesn't have a direct source-branch ignore filter, but the best approach is to use reviews:
auto_review:
ignore_title_keywords:
- "Crowdin"This will skip any PR whose title contains "Crowdin" (case-insensitive), which covers all auto-generated Crowdin update PRs. Alternatively, if you'd like to filter by the Crowdin bot's GitHub username instead, you can use: reviews:
auto_review:
ignore_usernames:
- "<crowdin-bot-username>"The ✏️ Learnings added
🧠 Learnings used |
1 participant
Summary by CodeRabbit