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>
16 lines
720 B
YAML
16 lines
720 B
YAML
# A real vigil (2025-10-31, clean year), distinct from the pre-existing
|
|
# all-saints.yml (Nov 1). Own proper collect, generic enough that it
|
|
# doesn't name any particular saint, no unique antiphon of its own.
|
|
id: vigil-of-all-saints
|
|
name: "Vigil of All Saints"
|
|
rank: vigil
|
|
vigilOf: all-saints
|
|
common: common-of-a-vigil
|
|
propers: "vigil-of-all-saints"
|
|
# P/T/S/N: not confirmed via this pass's own file parser (this vigil's
|
|
# particular file format wasn't handled by it), but every other vigil on
|
|
# this calendar shares common-of-a-vigil (live-query-verified via the
|
|
# Vigil of St. Andrew/St. Bartholomew, see that section of TODO.md) --
|
|
# wired directly on that overwhelming precedent.
|
|
minorHoursCommon: common-of-a-vigil
|