Accept named calendar presets as a request parameter #40

New issue

Open

opened 2026-07-01 00:58:46 +00:00 by manlycucumber · 0 comments

manlycucumber commented

2026-07-01 00:58:46 +00:00

(Migrated from github.com)

Problem

Clients currently must assemble calendar parameters by hand. They need to request a named preset (SSPX, FSSP, ICKSP, Generic) directly, which the Api resolves to the underlying Core calendar configuration.

Acceptance criteria

A preset parameter accepts the supported preset names and resolves each to Core's calendar configuration.
Unknown preset names return the canonical error shape.
Preset and explicit-calendar parameters cannot conflict (clear precedence or rejection).
Preset resolution is covered by tests for each supported preset.

Notes

Presets are thin name-to-config mappings; the calendar logic stays in Core.

## Problem Clients currently must assemble calendar parameters by hand. They need to request a named preset (SSPX, FSSP, ICKSP, Generic) directly, which the Api resolves to the underlying Core calendar configuration. ## Acceptance criteria - [ ] A preset parameter accepts the supported preset names and resolves each to Core's calendar configuration. - [ ] Unknown preset names return the canonical error shape. - [ ] Preset and explicit-calendar parameters cannot conflict (clear precedence or rejection). - [ ] Preset resolution is covered by tests for each supported preset. ## Notes Presets are thin name-to-config mappings; the calendar logic stays in Core.

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#40

No description provided.

Rows
Columns