Repository navigation
feat(availability): platform and clinic closure calendar that blocks slot generation - #195
Conversation
|
@Philcsweb3 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
✅ Malware scan: cleanThe earlier findings are resolved as of |
|
@Philcsweb3 The malware scan flagged |
|
@Philcsweb3 This PR now has merge conflicts with git fetch upstream # upstream = https://github.com/DocForum/docforum-core.git
git rebase upstream/main
# resolve the conflicts, re-run the tests, then:
git push --force-with-leaseThe usual culprits are shared files like Automated message. It won't repeat unless the PR conflicts again after your next push. |
|
@Philcsweb3 CI is failing on this branch against the latest Backend (typecheck + test + build)
|
Overview
This PR adds an admin-managed closure calendar (platform-wide or per facility/location) that is applied during slot generation and to already-open slots, so patients can no longer book on days the building is closed. Booked appointments falling inside a new closure are reported for manual handling and are never auto-cancelled.
Related Issue
Closes #
Changes
📅 Closure Calendar in Availability Module
[MODIFY]
backend/src/modules/availability/services/index.tsClosurePeriod(platform-wide or matching the facility/location), with all-day closures handled time-zone-correctly.[MODIFY]
backend/src/modules/availability/validation.ts[MODIFY]
docs/api/README.mdVerification Results
(Output to be pasted from the CI run — booking, referral, order and payment flows are covered by integration tests per
AGENTS.md.)ClosurePeriodmodel, generation skip, admin CRUD + client listdocs/api/README.mdROADMAP.mdupdated (item status + changelog line)ARCHITECTURE.md§4 /docs/api/README.mdupdated if models or endpoints changedCloses #131