M1.11: English message catalog for every UI string

ui/src/i18n: en.json (20 flat dotted keys) and t(key, params?) with
{name} interpolation; a missing key warns in dev and returns the key.
All template text, title/aria-label attributes, notices and frontend
error texts go through t. ESLint vue/no-bare-strings-in-template is an
error. Catalog tests: interpolation, missing key, every t() key exists,
no unused keys. Engine messages stay English (G14). Docs updated.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
danny 2026-10-16 06:39:42 +02:00
parent 851d438e2a
commit 7c0fb312f6
21 changed files with 273 additions and 37 deletions

View file

@ -4,6 +4,10 @@
* Type-aware TypeScript rules apply to `.ts` and `.vue` files. Floating and
* misused promises are errors so that no rejection goes unhandled, `any`
* is an error, and inline comments are banned in favour of TSDoc blocks.
*
* Templates may not contain bare text: every interface string comes from the
* message catalog (`src/i18n`). The rule's default punctuation allowlist is
* extended by `;`, `…` and `×`.
*/
import js from "@eslint/js";
import { defineConfig } from "eslint/config";
@ -33,6 +37,15 @@ export default defineConfig(
"@typescript-eslint/no-misused-promises": "error",
"@typescript-eslint/no-explicit-any": "error",
"no-inline-comments": "error",
"vue/no-bare-strings-in-template": [
"error",
{
allowlist: [
"(", ")", ",", ".", "&", "+", "-", "=", "*", "/", "#", "%", "!", "?", ":", "[", "]",
"{", "}", "<", ">", "|", ";", "·", "•", "‐", "–", "—", "−", "…", "×",
],
},
],
},
},
{