flutter-l10n-audit

To audit hardcoded strings in your Flutter project, scan the lib/ directory to locate user-facing texts across UI elements. This process detects unlocalized texts embedded directly in Dart code, validating them against localization principles to prepare for ARB extraction.

Preparing a Flutter app for ARB extraction involves auditing hardcoded strings against localization guidelines and glossary terms. This generates a prioritized findings report that guides remediation before merging texts into app_en.arb.

You can check Dart code for i18n readiness during code reviews by running a localization audit. This functions as a preflight check to identify hardcoded user-facing texts and ensure consistency with defined text principles before translation handoff.

The Flutter localization audit validates extracted strings against specific glossary terms and localization principles. It enforces checks documented in the flutter-l10n-agent.md file to ensure findings meet required quality standards.

Scanning a Flutter project for l10n issues limits the audit to code within the lib/ directory and ARB readiness. It targets user-facing texts rather than internal logic strings, ensuring findings are relevant for localization workflows.

Auditing Flutter texts before the translation pipeline ensures localization quality and consistency. It identifies hardcoded strings and validates them against text principles, producing a remediation report that prevents translation errors.