Check React localization in code review

Use extraction, catalog checks, TypeScript, and the application build to catch different localization defects before merge.

A React message change reaches readers through source code, extraction, a target catalog, and the application's loader. Review that chain alongside the wording. A correct translation under a stale identity is never displayed; a source fallback can conceal a missing translation while leaving the screen usable.

This method covers the current React package with CLI-extracted JSONC catalogs. Use the project's own build and rendering checks around the CLI's extraction checks.

Inspect the source change first #

Read the new source message as an instruction or statement to the user. Then read its context. “Button” describes a shape; “Cancel a scheduled payment before submission” explains the action whose meaning must survive. Both source and context participate in identity, so a context-only edit can require a new target entry.

Review placeholders as values with a stable purpose. A translator must be able to reorder a person's name or amount without changing its identity. For rich text, keep navigation and component behavior in code while translating the sentence around the named tags. Messages and Rich text give the exact APIs.

Check extraction before checking targets #

From the intended project directory, with the CLI installed:

sh
lingo extract --check
lingo check

Use the same --src, --source-locale, --out, and --types options as the project's extraction command. The source locale defaults to en; the localization configuration does not change that command default. Follow with the repository's TypeScript check and production build, with generated declarations included.

Defect to introduce in a local review fixtureGate and expected evidence
Change a source message without regenerating catalogs or declarations.extract --check compares generated output and fails when it is stale.
Omit required context in an extracted message.check reports the extraction/context issue; inspect the source to repair the meaning.
Leave a missing or empty entry in an existing target JSONC catalog.check reports the discovered catalog's missing translation.
Leave generated declarations stale.Extraction/checking detects the generated mismatch; TypeScript separately checks application use.
Break a locale import or framework integration.The application's real build should expose the integration failure.

Use a local fixture when establishing these checks for the first time. extract --check succeeds when no source files are found, so confirm the reported directory contains the intended code. Otherwise a green result can mean the check inspected nothing.

Check required locale coverage explicitly #

When the files patterns in .lingo/config.json match the source catalog (for example locales/en.jsonc), lingo check also requires every configured target locale file. The pattern lingo init --yes writes, locales/en.json, does not match a .jsonc catalog, so with it only the React checks run. It reports a missing key only inside existing JSONC targets. Compare the required locale list with the files and imports as part of review. Temporarily remove a target entry in a local fixture to see how source fallback appears on the screen.

Read representative source/target pairs for meaning, especially changed promises and product terms. A clean JSONC consistency check does not assess that meaning. ARB, Android XML, Apple catalogs, and static documents require their native validation rather than this React-specific coverage check.

Resolve the diff without destroying reviewed output #

Regenerate stale output with lingo extract, inspect added and orphaned entries, and translate the required delta. Preserve reviewed target wording and the localization lock. Removing orphaned entries changes catalogs and should be reviewed separately from the source message change.

Choose whether translations arrive on the source branch or through a separate translation PR. The CI guide explains the delivery tradeoffs and managed App differences. In either pattern, keep merge permission separate from run permission and content acceptance.

Finish by loading the changed screen in a target locale with representative values. Follow rich links, inspect fallback behavior, and compare the displayed message with its intended action. The review is complete when both the program's message path and the wording have been examined.