Serve a single liturgical day via /v1 calendar endpoint #9

New issue

Closed

opened 2026-07-01 00:57:38 +00:00 by manlycucumber · 1 comment

manlycucumber commented

2026-07-01 00:57:38 +00:00

(Migrated from github.com)

Problem

The most basic and most-requested read is a single liturgical day for a given date, system, and calendar. This endpoint anchors the whole service and the static-generation hot path.

Acceptance criteria

A /v1 endpoint returns the resolved liturgical day for a valid (date, system, calendar) tuple.
The response uses the canonical envelope and includes the data-version stamp.
Unsupported or out-of-range dates return the canonical error shape.
The endpoint is covered by tests for several known feast days.

Notes

Traditional Roman calendars only.

## Problem The most basic and most-requested read is a single liturgical day for a given date, system, and calendar. This endpoint anchors the whole service and the static-generation hot path. ## Acceptance criteria - [ ] A `/v1` endpoint returns the resolved liturgical day for a valid (date, system, calendar) tuple. - [ ] The response uses the canonical envelope and includes the data-version stamp. - [ ] Unsupported or out-of-range dates return the canonical error shape. - [ ] The endpoint is covered by tests for several known feast days. ## Notes Traditional Roman calendars only.

manlycucumber commented

2026-07-03 05:39:45 +00:00

(Migrated from github.com)

Delivered as the skeleton's anchor in #133 and rounded out with its siblings in #134.

manlycucumber referenced this issue from a commit

2026-08-05 19:02:25 +00:00

feat: month, year, and discovery endpoints (#134)

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

Directorium/Api#9

No description provided.

Rows
Columns