[Epic] Calendar endpoints #8

New issue

Closed

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

manlycucumber commented

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

(Migrated from github.com)

Epic — child issues are tracked as sub-issues.

AC amendment (roadmap v3): include the fasting/abstinence field on calendar/day responses (surfacing Core v0.4 data).

Expose the core calendar read endpoints — single day, month, and year — over Core's traditional Roman calendars. Done when a client can fetch any liturgical day or range as JSON for a supported calendar/system. _Epic — child issues are tracked as sub-issues._ --- **AC amendment (roadmap v3):** include the **fasting/abstinence** field on calendar/day responses (surfacing Core v0.4 data).

manlycucumber commented

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

(Migrated from github.com)

Epic complete — /v1/day, /v1/month, /v1/year, and /v1/meta (discovery) all land over the single Core boundary. A month/year is one memoised resolution; discovery is derived from Core, not hardcoded. #133 + #134.

Epic complete — `/v1/day`, `/v1/month`, `/v1/year`, and `/v1/meta` (discovery) all land over the single Core boundary. A month/year is one memoised resolution; discovery is derived from Core, not hardcoded. #133 + #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#8

No description provided.

Rows
Columns