diff options
Diffstat (limited to 'test/cli.t')
| -rw-r--r-- | test/cli.t | 65 |
1 files changed, 65 insertions, 0 deletions
@@ -259,3 +259,68 @@ tree to read dune-project from. It is asserted in the Makefile's release target instead, which rewrites both and then requires the freshly built binary to report the version it just wrote -- the point in time where a drift between the two could actually be introduced. + +A user-supplied overlay is applied ON TOP of the shipped universal calendar, +never instead of it. That ordering is the point: data/ef/adjustments.sexp +carries RG 110's own 30 June companion, the Major Litanies, St Barbara and +Rogation Wednesday, and a user file that replaced it would silently drop all +four while appearing merely to add a local feast. + +A fixed-date local patron, observed on its own day: + + $ colitur day 2026 --overlay fixtures/overlay-example-diocesan.sexp | grep '^2026-07-11 ' + 2026-07-11 saturday time-after-pentecost 6 example-local-patron class-3 white +pius-i + +A MOVABLE one -- the capability the Date_spec work existed to unlock. "The +first Sunday of October" is the shape a patronal or dedication feast usually +takes, and it lands on a different civil date every year: + + $ for y in 2026 2027 2028; do colitur day $y --overlay fixtures/overlay-example-diocesan.sexp | grep 'example-dedication'; done + 2026-10-04 sunday time-after-pentecost 19 example-dedication class-1 white +ef-time-after-pentecost-sunday-19 + 2027-10-03 sunday time-after-pentecost 20 example-dedication class-1 white +ef-time-after-pentecost-sunday-20 + 2028-10-01 sunday time-after-pentecost 17 example-dedication class-1 white +ef-time-after-pentecost-sunday-17 + +The shipped calendar is untouched without the flag -- the same date, no local +feast, the ordinary Sunday restored: + + $ colitur day 2026 | grep '^2026-10-04 ' + 2026-10-04 sunday time-after-pentecost 19 ef-time-after-pentecost-sunday-19 class-2 green + +And the shipped overlay's own entries survive alongside the user's, which is +what "on top of, not instead of" means in practice: + + $ colitur day 2024 --overlay fixtures/overlay-example-diocesan.sexp | grep -c 'rogation-wednesday' + 1 + +An unreadable overlay is fatal, not a warning: a calendar that failed to load +is not something to carry on past. + + $ colitur day 2026 --overlay /nonexistent/diocese.sexp + colitur: failed to load /nonexistent/diocese.sexp: /nonexistent/diocese.sexp: No such file or directory + [2] + +--overlay is refused on the commands it could not affect, rather than accepted +and silently ignored. `easter` reads no calendar data at all, and `temporal` +runs the temporal cycle before any sanctoral layer exists: + + $ colitur easter 2026 --overlay fixtures/overlay-example-diocesan.sexp + colitur: --overlay has no effect on `easter` (it reads no sanctoral data); refusing rather than ignoring it + [2] + + $ colitur temporal 2026 --overlay fixtures/overlay-example-diocesan.sexp + colitur: --overlay has no effect on `temporal` (it reads no sanctoral data); refusing rather than ignoring it + [2] + +A flag needing a value, given none: + + $ colitur day 2026 --overlay + colitur: --overlay needs a file path + colitur: usage: colitur easter <year> | colitur temporal <year> | colitur day <year> | colitur readings <year> (try: colitur --help) + [2] + +An unknown option is rejected rather than treated as a positional word: + + $ colitur day 2026 --diocese + colitur: unknown option --diocese + colitur: usage: colitur easter <year> | colitur temporal <year> | colitur day <year> | colitur readings <year> (try: colitur --help) + [2] |