feat: apply commemoration limits and ordering per day class (#36) #352
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!352
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/36-commemoration-limits"
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 #36. Epic #29, issue 7/8.
What
commemorationLimit()(interface + 1962 impl) — the day's admitted count:the celebrated office's class count from
Calendar\CommemorationLimit(I: 1, II: 1, III/IV: 2), reduced to 0 on days that admit none (the
Triduum, the privileged octaves, the first-class vigils).
isPrivilegedCommemoration()promoted to the interface (n. 108).Precedence\CommemorationSelector— orders the day's commemorationcandidates privileged first (so a tight count keeps them), then by tier,
then by id, and trims to the limit, dropping the rest (n. 114).
The whole-year sweep that gathers the candidates and calls this is #37.
Verification
composer lint·composer analyse(PHPStan L6, no errors) ·composer test(461 tests, 30,303 assertions — +10). Commits signed + DCO.