Placeholder Integrity Check
The placeholder check verifies that dynamic tokens remain intact between source and target strings.
Examples
{ "hello": "Hello {name}" }
{ "hello": "Bonjour {username}" }Why this matters
Changed placeholders can break runtime interpolation or show incorrect dynamic values. Treat this as a file integrity issue, not a translation-style issue.
How the check works
LocaleQA extracts placeholder tokens from matching source and target paths and compares token names and counts the same way on every scan.
Where judgment still matters
The check validates token preservation. It does not evaluate grammar around the token or pluralization quality.
How to use the finding
LocaleQA reports the affected JSON path, the source and target values involved, and the rule that triggered the finding. Developers, localization PMs, vendors, and QA reviewers can use that as a specific file-level item to fix, approve, or discuss before release.
Some findings are valid exceptions. A migration file, documented style choice, or locale-specific convention may explain the difference. In those cases, teams can leave the string as-is or disable the check for that scan.
LocaleQA is JSON file QA. It does not judge wording or rewrite translations; it surfaces the file issue so the responsible owner can decide the right fix.