mirror of
https://git.pumpin.online/funkpower/typikon.git
synced 2026-10-22 18:57:13 +00:00
funkpower
33441113ce
There is one engine and nine doors into it, and nothing until now checked that the doors agree. CI tested each binding against itself: the Python wheel imported, the C demo compiled, the npm package type-checked. None of that would have caught a field that crosses one boundary wrong, which is the failure this library is most exposed to, because a wrong answer about a fast day looks exactly like a right one. So: twelve days, chosen where the bindings could plausibly differ, and all twenty-two fields compared against what the command line says. The days are Pascha itself, the Nativity on both calendars, a Wednesday of the Great Fast under Byzantine Catholic law and again at the Typikon, a weekday of the Nativity Fast where Greek and Slavic usage part, the one Orthodox church on the Gregorian Paschalion, and a day with no feast. A release now runs what a push runs. It had been gated on cargo test alone, so the C ABI, the Lua binding, the Python parity check and the README examples were checked on the branch that led to a release and not on the release. Neither registry will reuse a version, so the gate belongs before the upload. Writing it found three things. The npm exports map did not expose the wasm by package path, so a bundler asked for typikon/web/typikon_bg.wasm was told no such path exists and had to reach into node_modules; the documented init() call was never affected. The suite could hang instead of fail, because the test web server was backgrounded inside a subshell and killed by job spec, leaving bash in do_wait forever. And pointing XDG_CONFIG_HOME at a path that does not exist isolates typikon and breaks every other program that keeps state under it, a browser included. A surface whose toolchain is missing is named as skipped, and fewer than three surfaces running is a failure rather than a pass, so a container with nothing installed cannot come out green.
37 lines
1.7 KiB
TypeScript
37 lines
1.7 KiB
TypeScript
// TypeScript, compiled under --strict and then run. Every field is annotated
|
|
// on the way out, so a type that has drifted from what the package returns is
|
|
// a compile error rather than a surprise at run time.
|
|
import { readFileSync, writeFileSync } from "node:fs";
|
|
import { describeIso, week, pascha, jurisdictions, type Day, type Options } from "typikon";
|
|
|
|
const [probesPath, outPath] = process.argv.slice(2);
|
|
type Probe = [string, string, boolean];
|
|
|
|
const out: Record<string, Record<string, unknown>> = {};
|
|
for (const [date, jurisdiction, typikon] of JSON.parse(readFileSync(probesPath, "utf8")) as Probe[]) {
|
|
const options: Options = { jurisdiction, typikon };
|
|
const d: Day = describeIso(date, options);
|
|
const season: string | null = d.season;
|
|
const commemorations: string[] = d.commemorations;
|
|
const daysToPascha: number = d.daysToPascha;
|
|
out[`${date}|${jurisdiction}|${typikon ? 1 : 0}`] = {
|
|
date: d.date, weekday: d.weekday, jurisdiction: d.jurisdiction,
|
|
calendar: d.calendar, churchDate: d.churchDate, season,
|
|
cycle: d.cycle, feast: d.feast, rank: d.rank, sign: d.sign,
|
|
tradition: d.tradition, title: d.title, commemorations,
|
|
fast: d.fast, fastLabel: d.fastLabel, emoji: d.emoji, reason: d.reason,
|
|
obligation: d.obligation, binds: d.binds, pascha: d.pascha,
|
|
daysToPascha, julianOffset: d.julianOffset,
|
|
};
|
|
}
|
|
|
|
// The rest of the surface, so nothing is typed only where it is called.
|
|
const seven: Day[] = week(new Date(2026, 3, 12), 7, { jurisdiction: "moscow" });
|
|
const p: Date = pascha(2027, "old");
|
|
const keys: string[] = jurisdictions().map((j) => j.key);
|
|
if (seven.length !== 7 || p.getFullYear() !== 2027 || keys.length < 20) {
|
|
throw new Error("the rest of the surface did not answer");
|
|
}
|
|
|
|
writeFileSync(outPath, JSON.stringify(out));
|