Wire Core into the Api service as the single data source #6

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

Problem

Api is a thin HTTP service over Core; it must call Core to compute liturgical data rather than reimplementing any logic. A clean integration boundary is needed so Api never embeds calendar rules.

Acceptance criteria

  • Core is consumed via a single adapter/service boundary in Api.
  • Api contains no liturgical computation logic of its own (only request/response handling and caching).
  • A smoke test resolves a known date through Core and returns it via an endpoint.
  • The adapter surfaces Core errors as the canonical Api error shape.

Notes

Api is AGPL-3.0-or-later over Core; never duplicate Core rules into Api.

## Problem Api is a thin HTTP service over Core; it must call Core to compute liturgical data rather than reimplementing any logic. A clean integration boundary is needed so Api never embeds calendar rules. ## Acceptance criteria - [ ] Core is consumed via a single adapter/service boundary in Api. - [ ] Api contains no liturgical computation logic of its own (only request/response handling and caching). - [ ] A smoke test resolves a known date through Core and returns it via an endpoint. - [ ] The adapter surfaces Core errors as the canonical Api error shape. ## Notes Api is AGPL-3.0-or-later over Core; never duplicate Core rules into Api.
manlycucumber commented 2026-07-03 05:31:32 +00:00 (Migrated from github.com)

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

Delivered in #133 (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#6
No description provided.