Serve a full liturgical month via /v1 calendar endpoint #10

Closed
opened 2026-07-01 00:57:41 +00:00 by manlycucumber · 1 comment
manlycucumber commented 2026-07-01 00:57:41 +00:00 (Migrated from github.com)

Problem

Clients building monthly views need every day in a month in one request rather than 28–31 separate calls. A month endpoint reduces request volume and aligns with the printable Ordo work later.

Acceptance criteria

  • A /v1 endpoint returns all days of a given month for a valid (year, month, system, calendar).
  • Days are ordered and each carries the same fields as the single-day response.
  • Invalid year/month combinations return the canonical error shape.
  • The endpoint is covered by tests asserting day count and boundary days.

Notes

Reuse the single-day projection so month and day responses stay consistent.

## Problem Clients building monthly views need every day in a month in one request rather than 28–31 separate calls. A month endpoint reduces request volume and aligns with the printable Ordo work later. ## Acceptance criteria - [ ] A `/v1` endpoint returns all days of a given month for a valid (year, month, system, calendar). - [ ] Days are ordered and each carries the same fields as the single-day response. - [ ] Invalid year/month combinations return the canonical error shape. - [ ] The endpoint is covered by tests asserting day count and boundary days. ## Notes Reuse the single-day projection so month and day responses stay consistent.
manlycucumber commented 2026-07-03 05:39:46 +00:00 (Migrated from github.com)

Delivered in #134 (squash-merged to develop).

Delivered in #134 (squash-merged to `develop`).
Sign in to join this conversation.
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#10
No description provided.