morningman opened a new pull request, #4248: URL: https://github.com/apache/doris-website/pull/4248
## Summary Introduce one state file per Japanese document at `translations/state/ja/pages/<pluginId>/<version>/<docId>.json`. The loader combines these files with the existing `docs.json` ledger, and a page file supersedes its legacy entry. This lets independent translation PRs add disjoint state paths instead of editing one shared JSON array. The existing `docs.json` stays readable during migration. This PR adds only the compatibility layer and schema marker; translation PRs can switch to page files after it merges. ## Integration - The site adapter and planner load the combined records. - Coverage and inventory audits read the committed aggregate, including page files. - PR validation and open-PR candidate reconciliation recognize changed page files. - The build-scope planner selects the Japanese locale and affected version for a state-only page-file change. ## Validation - `node --test scripts/i18n/__tests__/*.test.cjs`: 71 passed. - `node scripts/i18n/audit-coverage.cjs --source-ref HEAD`: passed before the final rebase; the existing Japanese coverage counts were unchanged by the compatibility layer. - `DORIS_ENABLE_JA=true node scripts/build-locale.cjs build ... ja`: passed after the site's key-features generation step, with existing document warnings. - `git diff --check upstream-apache/master...HEAD`: clean. ## Migration note Already-open translation PRs that still modify `docs.json` can still conflict with each other. They need separate conversion to page files or a state merge after this compatibility PR lands. New page-file PRs are independent at the state-file level. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
