Added error messages for bulk upload invalid delimiter [MOSIP-27141]

[GOKULRAJ136]

Summary by CodeRabbit

• Documentation
  • Added multilingual error messaging for invalid delimiter scenarios across seven languages: Arabic, English, Spanish, French, Hindi, Kannada, and Tamil. Users will now receive appropriately localized error messages when encountering delimiter validation issues.

[ase-101]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[coderabbitai]

Walkthrough

A new translation entry ADM-BLK-010 ("Invalid delimiter used") was added across seven language files in the admin internationalization bundle, introducing localized error messages for Arabic, English, Spanish, French, Hindi, Kannada, and Tamil.

Changes

Cohort / File(s)	Summary
New translation entry ADM-BLK-010 added artifacts/src/i18n/admin-i18n-bundle/i18n/ara.json, eng.json, es.json, fra.json, hin.json, kan.json, tam.json	Added ADM-BLK-010 error code with localized "Invalid delimiter used" message in all supported languages (Arabic, English, Spanish, French, Hindi, Kannada, Tamil). No other entries modified.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Homogeneous changes across all files (identical pattern repetition)
• Static translation string additions with no logic or control flow
• No functional impact; purely data extension

Poem

🐰 Hop hop, a new error found!
"Invalid delimiter" 'round the world goes 'round,
Seven tongues now speak the same,
ADM-BLK-010 marks the blame! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: adding error messages for bulk upload invalid delimiter across multiple i18n files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (3)

artifacts/src/i18n/admin-i18n-bundle/i18n/hin.json (1)

1420-1420: Hindi phrasing is fine; consider a more common term

Optional: swap “सीमांकक” with “विभाजक” for wider familiarity.

-        "ADM-BLK-010" : "अमान्य सीमांकक का उपयोग किया गया",
+        "ADM-BLK-010" : "अमान्य विभाजक का उपयोग किया गया",

artifacts/src/i18n/admin-i18n-bundle/i18n/kan.json (1)

1431-1431: Kannada wording: optional native term

If you prefer native wording over the loanword, consider:

-        "ADM-BLK-010" : "ಅಮಾನ್ಯವಾದ ಡಿಲಿಮಿಟರ್ ಬಳಸಲಾಗಿದೆ",
+        "ADM-BLK-010" : "ಅಮಾನ್ಯ ವಿಭಾಜಕವನ್ನು ಬಳಸಲಾಗಿದೆ",

artifacts/src/i18n/admin-i18n-bundle/i18n/es.json (1)

1302-1302: Spanish phrasing OK; optional refinement

Consider one of these slightly more standard variants:

• “Se ha utilizado un delimitador no válido”
• “Se usó un delimitador no válido”

Also, you can drop the space before the colon for consistency.

-        "ADM-BLK-010" : "Se utilizó un delimitador no válido",
+        "ADM-BLK-010": "Se ha utilizado un delimitador no válido",

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6ecfc65 and 596231b.

📒 Files selected for processing (7)

• artifacts/src/i18n/admin-i18n-bundle/i18n/ara.json (1 hunks)
• artifacts/src/i18n/admin-i18n-bundle/i18n/eng.json (1 hunks)
• artifacts/src/i18n/admin-i18n-bundle/i18n/es.json (1 hunks)
• artifacts/src/i18n/admin-i18n-bundle/i18n/fra.json (1 hunks)
• artifacts/src/i18n/admin-i18n-bundle/i18n/hin.json (1 hunks)
• artifacts/src/i18n/admin-i18n-bundle/i18n/kan.json (1 hunks)
• artifacts/src/i18n/admin-i18n-bundle/i18n/tam.json (1 hunks)

🔇 Additional comments (4)

artifacts/src/i18n/admin-i18n-bundle/i18n/fra.json (1)

1571-1571: Translation is correct; ignore space-before-colon suggestion

Verification confirms all JSON is valid, ADM-BLK-010 appears exactly once per locale, and the space before the colon is the consistent pattern throughout the codebase (all 7 locale files follow this convention). The suggested refactor to remove the space contradicts the actual codebase style.

Likely an incorrect or invalid review comment.

artifacts/src/i18n/admin-i18n-bundle/i18n/eng.json (1)

1301-1301: Localization entry for invalid delimiter error added correctly.

The new error code ADM-BLK-010 with message "Invalid delimiter used" is properly positioned in the serverError object following the existing ADM-BLK-009 entry. JSON syntax and structure are valid.

artifacts/src/i18n/admin-i18n-bundle/i18n/ara.json (1)

1352-1352: Arabic localization entry for invalid delimiter error added correctly.

The new error code ADM-BLK-010 with Arabic translation "تم استخدام فاصل غير صالح" is properly positioned and follows the same structure as the English entry. JSON syntax is valid.

artifacts/src/i18n/admin-i18n-bundle/i18n/tam.json (1)

1429-1429: Tamil localization entry for invalid delimiter error added correctly.

The new error code ADM-BLK-010 with Tamil translation "தவறான வரம்புக் குறி பயன்படுத்தப்பட்டது" is properly positioned and maintains consistency with the English and Arabic entries. JSON syntax is valid.