Expose supported systems, calendars, and languages as a discovery endpoint #12

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

Problem

Clients need to discover which systems, calendars, and languages are valid without hardcoding them. A discovery endpoint keeps clients in sync as Core adds rubric systems in later milestones.

Acceptance criteria

  • A /v1 endpoint lists supported systems, calendars, and languages with stable identifiers.
  • The list is derived from Core, not a hardcoded duplicate.
  • The response carries the data-version stamp.
  • The endpoint is covered by a test asserting the currently supported set.

Notes

Later milestones (1954/1955, presets) extend this list; the endpoint must reflect them automatically.

## Problem Clients need to discover which systems, calendars, and languages are valid without hardcoding them. A discovery endpoint keeps clients in sync as Core adds rubric systems in later milestones. ## Acceptance criteria - [ ] A `/v1` endpoint lists supported systems, calendars, and languages with stable identifiers. - [ ] The list is derived from Core, not a hardcoded duplicate. - [ ] The response carries the data-version stamp. - [ ] The endpoint is covered by a test asserting the currently supported set. ## Notes Later milestones (1954/1955, presets) extend this list; the endpoint must reflect them automatically.
manlycucumber commented 2026-07-03 05:39:49 +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#12
No description provided.