Files
siftlode/frontend/src/components/legal/legalBodies.contract.dom.test.tsx
T
peter 4aaaaa7860 chore(comments): drop epic, sprint and review-round ids from the code
The code cited its plan instead of saying why: `E28 review J4`, `(R6 S3b)`, `S1 justified…`,
`deep-review round 5`. That plan lives in the private ops repo, so for every reader of this one the
citation was noise, and a sentence whose subject was the plan step ("round 2 showed…") hid its
lesson behind an id. Each one is gone and the "why" kept: a bare citation is deleted, a sentence
carrying a lesson is reworded around it ("a later attempt showed…").

Measured (`scripts/audit_metrics.py`, product code): 652 lines in 270 files carried an epic code by
the definition the next commit holds (507 / 241 by the old, two-digit-only one) -> 0. Across all
code, tests, scripts and configs: ~1100 epic-code lines plus ~320 sprint/round ids.

Behaviour unchanged, checked mechanically: every changed .py file has the same AST once docstrings
are blanked; css/sh/toml/yml/json files are identical once comments are stripped; the only
non-comment changes in TS/JS are test titles, one description string in a contract table, and five
ESLint messages, whose text is all the gates snapshot diff holds. Not touched: Markdown (docs and
the changelog keep their history), Alembic migrations, TV episode notation (`S2 · E5`), DESIGN.md
ids (`C1`, `B4`, `S3h`), tracker ids (`SEC-16`, `DX-17`).

One stale claim fixed on the way: test_hls_reaper's docstring said the player checkpoints "every
10 s whether or not it is playing", which plex/stream.py calls wrong; it now says what the code does.
2026-10-05 00:19:39 +02:00

37 lines
1.4 KiB
TypeScript

// @vitest-environment jsdom
//
// The legal pages are written out once per language (a document, not UI strings — see LegalLayout).
// What keeps the two from drifting apart is this: both languages must have the SAME sections, in the
// same order, by anchor — so a section added to one (as the log sections were) cannot be
// missing from the other, and a link to `/privacy#diagnostics` lands in either language.
import { describe, expect, it, vi } from "vitest";
import { cleanup, render } from "@testing-library/react";
import type { ComponentType } from "react";
vi.mock("../../lib/http", () => ({ send: () => Promise.resolve({ ok: false }) }));
import { PrivacyEn, PrivacyHu } from "./PrivacyPolicy";
import { TermsEn, TermsHu } from "./Terms";
const sections = (Body: ComponentType) => {
const { container } = render(<Body />);
const ids = [...container.querySelectorAll("h2")].map((h) => h.id);
cleanup();
return ids;
};
describe("legal pages", () => {
it.each([
["privacy", PrivacyEn, PrivacyHu],
["terms", TermsEn, TermsHu],
])("%s has the same sections in Hungarian and English", (_name, En, Hu) => {
const en = sections(En);
expect(en.every(Boolean)).toBe(true);
expect(sections(Hu)).toEqual(en);
});
it("the privacy policy has the section the diagnostics consent links to", () => {
expect(sections(PrivacyEn)).toContain("diagnostics");
});
});