Files
DeepSeek-Reasonix/desktop/frontend-next/perf/i18n.mjs
T
yhh 394da0a313 refactor: the kernel's packages live in the layer they belong to
internal/ was 141 packages side by side, so nothing but a reader's memory
said which were foundations and which assembled the rest. Each now sits in a
layer directory, and the directory is the declaration:

  base      L0  foundation with no domain in it
  contract  L1  types and interfaces the layers above agree on
  model, tools, safety, ext, state, platform
            L2  subsystems, peers of one another
  runtime   L3  the turn engine
  session   L4  the controller
  assembly  L5  the composition root
  frontend  L6  cli, serve, acp and the host adapters

Only paths change: package names, code and behaviour do not. Imports,
repolint and coverage baselines, sensitive paths, CI package lists and docs
follow the new paths; release notes keep the paths they were written with,
and sample paths inside tests and fixtures keep theirs.

repolint gains layer-order: a package may import its own layer and those
below it, read from where it lives. The 47 imports that point upward today
are recorded as that rule's opening debt (-allow-widen, a new rule's first
baseline) and can only go down. Most of it is config, which still reaches
into eight subsystems and is the next thing to take apart; the rest is
event, history and a few tools reaching into runtime for types that belong
in contract.
2026-09-23 18:28:21 -07:00

95 lines
5.0 KiB
JavaScript
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
// 词表守卫:源码里每个 t("…") 的中文 key,英文词表都要有;反过来词表里也不
// 该留下源码已经不用的条目。缺翻译时界面会退回中文而不是空白,正因如此漏了
// 不会自己暴露 —— 这个检查就是替代品,对应 internal/base/i18n 的 catalog 测试。
import { readFileSync, readdirSync, statSync } from "node:fs";
import { join, dirname } from "node:path";
import { fileURLToPath } from "node:url";
const SRC = join(dirname(fileURLToPath(import.meta.url)), "..", "src");
function walk(dir) {
const out = [];
for (const name of readdirSync(dir)) {
const p = join(dir, name);
if (statSync(p).isDirectory()) out.push(...walk(p));
else if (/\.tsx?$/.test(name)) out.push(p);
}
return out;
}
// 词表本身是答案,扫它等于自问自答。词表不止 en.ts:en_kernel / en_remote /
// en_settings / en_window 都是它的一部分,而这里过去只排除了 en.ts —— 于是那三
// 张表里的每一条中文都被当成「源码在用、词表没有」,「缺译」那份名单里绝大多数
// 一直是这么来的。kernel.ts 不同,它的中文是码的原文,靠 t(变量) 消费。
const isTable = (f) => /[\\/]i18n[\\/]en(_[a-z]+)?\.ts$/.test(f);
const files = walk(SRC).filter((f) => !isTable(f) && !f.endsWith("i18n/index.ts"));
const CJK = /[一-鿿]/;
// 两类引用,判据不同:
// 强 —— t("中文"),key 就写在调用点上,必须有翻译,缺了就是错。
// 弱 —— 别处的中文字面量。常量表(档位名、分区名、状态名)走的是
// t(变量),静态分析看不见 key,所以这些串也要算「在用」,
// 否则它们的翻译会被误报成多余的。
const CALL = /\bt\(\s*(["'])((?:[^"'\\]|\\.)*?)\1/g;
const LITERAL = /(["'])((?:[^"'\\]|\\.)*?)\1/g;
const used = new Map();
const loose = new Set();
for (const f of files) {
const src = readFileSync(f, "utf8");
for (const m of src.matchAll(CALL)) {
if (CJK.test(m[2])) used.set(m[2], (used.get(m[2]) ?? new Set()).add(f.slice(SRC.length + 1)));
}
for (const m of src.matchAll(LITERAL)) if (CJK.test(m[2])) loose.add(m[2]);
}
// 中文是合法的 JS 标识符,词表里两种写法都有:`"占用": "…"` 和 `占用: "…"`。
// 只认带引号的那种,另一种就成了「源码在用、词表没有」——存储面板那六条一直被
// 这么误报,而一条永远红的守卫和一条永远绿的一样没用:它不再是在说源码的事。
// 行首两格、且不是注释:值的续行缩四格,注释以 // 开头,两者都不是键。
const KEY = /^ {2}(?!\/\/)(?:"((?:[^"\\]|\\.)*)"|([^\s:"'`,{}()[\]]+))\s*:/gm;
// 一行看着是键、却没被上面那条读出来,就是这个守卫看不懂自己的输入——它会安静
// 地把那一条报成「缺翻译」。读不出来的行要自己说出来,而不是等下一个人去比对。
// 两格开头而不是键的,只有两种:文件之间的展开(...EN_X),和注释。
const UNREAD = /^ {2}(?!\/\/|\.\.\.|[}\]])\S.*$/gm;
const have = new Set();
const opaque = [];
for (const f of readdirSync(join(SRC, "i18n")).filter((n) => /^en(_[a-z]+)?\.ts$/.test(n))) {
const body = readFileSync(join(SRC, "i18n", f), "utf8");
// 按起始位置比对,不按文本:一条键的文本可能是另一行的前缀,那样比会把没读
// 出来的行算成读出来了,正好放过这个守卫要抓的东西。
const read = new Set();
for (const m of body.matchAll(KEY)) {
have.add(m[1] ?? m[2]);
read.add(m.index);
}
for (const m of body.matchAll(UNREAD)) {
if (!read.has(m.index)) opaque.push(`${f}: ${m[0].trim().slice(0, 60)}`);
}
}
const missing = [...used.keys()].filter((k) => !have.has(k)).sort();
const unused = [...have].filter((k) => CJK.test(k) && !used.has(k) && !loose.has(k)).sort();
// fixture 与开发用文案不进界面,不必翻。
console.log(`t() 直接用的中文 key: ${used.size} 常量表等间接引用: ${loose.size} 英文词表: ${have.size}`);
// 同上:扫空了不是「全都翻好了」。
if (!used.size || !have.size) {
console.log("\n没扫到源码或词表:先确认 PERF_SRC 指对了地方。");
process.exit(1);
}
if (missing.length) {
console.log(`\n缺英文翻译 ${missing.length} 条:`);
for (const k of missing.slice(0, 40)) console.log(` ${k} ← ${[...used.get(k)][0]}`);
if (missing.length > 40) console.log(` …还有 ${missing.length - 40} 条`);
}
if (unused.length) {
console.log(`\n词表里源码已不用的 ${unused.length} 条(既没 t() 引用,也不在任何中文字面量里):`);
for (const k of unused.slice(0, 20)) console.log(` ${k}`);
}
if (opaque.length) {
console.log(`\n词表里这 ${opaque.length} 行读不出键来——它们会被当成「没这条翻译」:`);
for (const l of opaque.slice(0, 20)) console.log(` ${l}`);
}
if (!missing.length && !unused.length && !opaque.length) console.log("\n词表与源码一致");
process.exit(missing.length || opaque.length ? 1 : 0);