Repository navigation
Allow untranslated localization handbacks with English fallback - #127
Conversation
Keep locale coverage, source validation, and staged output checks while removing translation-completeness gating. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Consumer pin updates are pushed; seven follow-up PRs are draft and existing environments #1971 is updated.
Validation completed against this exact shared revision: actual YAML contract guards passed for all eight consumers; all 24 YAML files passed formatting. Fourteen enabled native Azure previews passed with publication disabled. Both environments YAMLs also expanded through an enabled isort definition; native environments definitions remain disabled. Real current isort dev handback import produced all 28 required locale files with English fallback. Shared CI is green, including Python 3.10–3.14 tests on Windows and Linux. Merge this shared fix before consumer pin changes. No PRs merged, release builds queued, or extension publication performed. |
|
🔒 Automated review in progress — Rich Chiodo (@rchiodo) is auto-reviewing this PR. |
Summary
Allow untranslated strings, including wholly untranslated locale tables, to use English until translations arrive. Keep missing/duplicate locale, empty source/table, malformed input, and invalid generated JSON checks. Import remains staged before source mutation.
Verification
All 29 standard-library localization/Git regression tests passed, along with Black/isort/Flake8. Real pinned l10n-dev import of current isort dev handbacks generated all 28 tables; all 13 real languages retain English manifest/runtime text. No release or publication was triggered.
Consumer release pins must be updated to this reviewed revision. This changes the earlier translation-readiness policy at the user request; English fallback is acceptable.