feat: represent commemorations and the displaced set (#26) #342
No reviewers
Labels
No labels
area: build
area: ci
area: compare
area: data
area: engine
area: model
area: provenance
area: rite
area: validation
backport
blocked
breaking
confirmed
dependencies
duplicate
epic
github_actions
invalid
needs-info
needs-triage
php
priority: high
priority: low
priority: medium
regression
type: bug
type: chore
type: correction
type: docs
type: enhancement
type: feature
type: fix
type: perf
type: refactor
type: security
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Directorium/Core!342
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/26-commemoration-displaced"
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?
Closes #26. Epic #23, issue 3/6.
What
Makes the day-roles and the 1960 commemoration limits representable — the
overlay does not decide them (that is the resolver, #29):
Calendar\CelebrationRole— the four roles aLiturgicalDaygroupsoffices into: celebration, commemoration, displaced, tempora.
Calendar\RoledObservance— a realized office paired with its role. Itkeeps the whole
RealizedObservance, so a displaced office retains all thedata the transfer queue (#34) needs to re-place it, and a commemoration
keeps everything needed to render it.
Calendar\CommemorationLimit::forDayClass()— the 1960 counts: class I → 1(privileged only), II → 1, III/IV → 2. (The privileged-only restriction and the
zero-commemoration days are enforced in #29/#36.)
Verification
composer lint·composer analyse(PHPStan L6, no errors) ·composer test(382 tests, 16,510 assertions — +14). Commit numbers cited-verified in the design
pass (Code of Rubrics). Commits signed + DCO.