Built-in scheme library: decide scope (~57 keys vs spec's ~200) and add World Pride Day #49
Labels
No labels
area/ai
area/backend
area/frontend
area/infra
area/scheduler
area/wled
good-first-issue
priority/high
priority/low
priority/medium
type/bug
type/chore
type/ci-cd
type/docs
type/feature
type/qa
v1.0.0
v1.1.0
v1.2.0
v2.0.0
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
rbrooks/Iris-WLED#49
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Split from #40.
schemes/builtin.yamlhas 45event_keys+ 12tags= ~57 mappings; spec §3.3 says the curated library "covers ~200 major events." Current coverage = bundled events + US federal holidays + tag fallbacks; nothing beyond (no Kwanzaa, Cinco de Mayo, Rosh Hashanah, Nowruz, Mid-Autumn Festival, non-US holidays via Calendarific, …).Decide explicitly:
Either way:
config/events.yamlalongside (Kwanzaa, Rosh Hashanah/Yom Kippur, Cinco de Mayo, Mid-Autumn Festival are cheap wins with existing recurrence types)Picking this up (Wave 2). Scope decision: option (a) — amend spec §3.3 to describe the actual design (curated bundled events + US federal holidays + tag fallbacks + AI for the long tail), rather than claim ~200 hand-curated entries. Plus fill the one §15-named gap (World Pride Day, Jun 28) and the cheap recurrence-type wins (Kwanzaa, Rosh Hashanah/Yom Kippur, Cinco de Mayo, Mid-Autumn Festival). Branch
fix/49-scheme-libraryoff main.