CMG-1057, CMG-1058 | Language Mapper and Locale Migration Fixes

[chetan-contentstack]

🔗 Jira Ticket

CMG-1057 · CMG-1058

---

📋 PR Type

• ✨ Feature
• 🐛 Bug Fix
• 🔥 Hotfix
• ♻️ Refactor
• 🧹 Chore / Dependency Update
• 📝 Documentation

---

📝 Description

What changed?

CMG-1057 — Language mapper (Step 2) fixes for delta restart:

• Already-mapped locales no longer appear as selectable options in dropdowns on restart iteration
• Add Language button no longer gets stuck disabled after adding one language — now stays available until all source locales are mapped
• Newly-added rows in a restart iteration remain editable until the user advances past Step 2, so a wrong selection can be corrected without being locked immediately

CMG-1058 — Delta migration correctness and UI fixes:

• New locales added in a delta iteration now correctly localize existing Contentstack entries rather than creating duplicate new entries
• Entry mapper Save button is now visible whenever there is table data, not only when total counts are non-zero
• Entry mapper footer is sticky so the Save button is not clipped below the viewport
• Step 1 → Step 3 skip guard tightened to also require all source locales to be mapped, preventing Step 2 (locale mapping) from being bypassed

Why?

On a delta restart with extra locales added, the language mapper was showing already-consumed locales in dropdowns and blocking the user from adding more than one new language. On migration, new-locale entries were being imported as fresh entries (new UIDs) instead of being added as localizations to the entries created in the first iteration, breaking the localization relationship entirely.

---

🧩 Affected Areas

• api — Node.js backend
• ui — React frontend
• upload-api — Upload API server
• docker / docker-compose
• CI / GitHub Actions workflows
• Environment variables / config

---

🧪 How to Test

CMG-1057:

1. Complete a first iteration with only the master locale mapped
2. Start a second iteration (restart) on Step 2
3. Verify already-mapped locales do not appear in source/destination dropdowns
4. Add two new languages — verify the Add Language button stays enabled after the first addition
5. Select both dropdowns for a newly added row — verify the row stays editable (not immediately disabled) so you can correct a wrong pick

CMG-1058:

1. Run a first iteration migration with only the master locale
2. Start a second iteration, add two new locales on Step 2, and complete the migration
3. In Contentstack, verify the entries from iteration 1 now have localizations in the two new locales (same UIDs as the master locale entries, not new UIDs)
4. On the entry mapper step, verify the Save button is visible and the footer does not disappear below the viewport

Expected result: No duplicate entries created for new locales; existing entries gain locale variants. Language mapper dropdowns filter correctly and rows remain editable until saved.

---

📸 Screenshots / Recordings

Before	After
Already-mapped locales visible in dropdown	Mapped locales filtered out
Add Language disabled after one addition	Button stays enabled for additional locales
New-locale migration creates new entries (different UIDs)	New-locale migration localizes existing entries (same UIDs)

---

🔗 Related PRs / Dependencies

---

✅ Author Checklist

• Branch follows naming convention: feature/, bugfix/, or hotfix/ + 5–30 lowercase chars
• Jira ticket linked above
• Self-reviewed the diff — no debug logs, commented-out code, or TODOs left in
• .env / example.env updated if new environment variables were added
• No sensitive credentials or secrets committed
• Existing tests pass locally (npm test)
• New tests written (or not applicable — explain why)
• README.md / docs updated if behaviour changed
• Talisman pre-push scan passes (no secrets flagged)

---

👀 Reviewer Notes

• The core backend change is in api/src/utils/entry-update.utils.ts — the removeEntriesFromDatabase function previously skipped new-locale directories entirely (continue), leaving their entries in the import data for the CLI to create as fresh entries. It now falls through and routes any entry with a known Contentstack UID into the localize path (entriesToUpdate), removing it from import data to prevent duplication.
• All language mapper locking logic is in LoadLanguageMapper.tsx. The key invariant: locale.value is only set on rows rebuilt from a prior iteration's saved mapping; newly-added rows always have value = '', so isDisabled && !!locale.value correctly locks only rebuilt rows.

---

Migration v2 · Docs · Issues

[github-actions]

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type	Count (with fixes)	Without fixes	Threshold	Result
🔴 Critical Severity	1	0	10	✅ Passed
🟠 High Severity	2	382	25	✅ Passed
🟡 Medium Severity	0	0	500	✅ Passed
🔵 Low Severity	1	0	1000	✅ Passed

⏱️ SLA Breach Summary

✅ No SLA breaches detected. All vulnerabilities are within acceptable time thresholds.

Severity	Breaches (with fixes)	Breaches (no fixes)	SLA Threshold (with/no fixes)	Status
🔴 Critical	0	0	15 / 30 days	✅ Passed
🟠 High	0	0	30 / 120 days	✅ Passed
🟡 Medium	0	0	90 / 365 days	✅ Passed
🔵 Low	0	0	180 / 365 days	✅ Passed

ℹ️ Vulnerabilities Without Available Fixes (Informational Only)

The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:

• Critical without fixes: 0
• High without fixes: 382
• Medium without fixes: 0
• Low without fixes: 0

✅ BUILD PASSED - All security checks passed