will
79372fb274
At Vespers/Compline, a day's own Vigil losing tonight to tomorrow's First Vespers was showing up as a redundant extra commemoration alongside that same feast (e.g. Nov 29's Compline showing both "St. Andrew" and "Vigil of St. Andrew" for Advent I's anticipated evening). Added an explicit `vigilOf` field to each Vigil's own saint record (several Vigil ids don't map cleanly to their feast's id by stripping a `vigil-of-` prefix — `vigil-of-the-assumption` vs `assumption`, `vigil-of-st-james` vs `st-james-the-greater` — so this needs to be explicit rather than guessed from the id or date adjacency). calendar/vespers.ts's evening-anticipation merge now skips adding the Vigil commemoration when tomorrow's winner or its own commemorations already include that same feast. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
18 lines
580 B
YAML
18 lines
580 B
YAML
# A real vigil (2025-11-29, clean year). No unique collect: the raw
|
|
# file's own [Oratio] is a plain cross-reference to a generic Common
|
|
# formula (@Commune/C1v, "Oratio 2 loco"), not unique text, so
|
|
# propers: null is correct (Common-of-Saints only) -- same treatment as
|
|
# October's Ss. Placid and Companions.
|
|
id: vigil-of-st-andrew
|
|
name: "Vigil of St. Andrew"
|
|
rank: vigil
|
|
vigilOf: st-andrew
|
|
common: common-of-a-vigil
|
|
propers: null
|
|
collectCommon: collect-c1v
|
|
collectName:
|
|
la: ["Andreas"]
|
|
en: ["Andrew"]
|
|
minorHoursCommon: common-of-a-vigil
|
|
benedictusCommon: common-of-a-vigil
|