Adds SlotModeFrozenTest (#[Group('slot-mode-frozen')]) locking three things
against the multi-resource booking phase:
- GET /api/v1/appointment-slots response shape
- GET /api/v1/appointment-settings/month-availability/{uuid} response shape
- public method signatures of SlotCalculatorService
Fixtures are structural, not raw snapshots: a fixed past date is rejected by
isWithinBookingWindow so an empty snapshot would prove nothing. Instead a
deterministic schedule on a computed near-future date, with epoch/uuid values
normalized to placeholders. What stays locked is the contract itself: keys,
ordering, types and local times.
No production code touched.
Task: docs/new_feture/taskes/task-00-service-mode-completion/
Slot-mode contract: unchanged (--group=slot-mode-frozen green, 3 tests)
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
17 lines
618 B
JSON
17 lines
618 B
JSON
{
|
|
"_readme": "READ-ONLY — قرارداد منجمد GET /api/v1/appointment-settings/month-availability/{doctorUuid}. فهرست روزها به «امروز» وابسته است و placeholder میگیرد؛ قرارداد، کلیدها و ترتیب و نوعهاست. رجوع: docs/new_feture/taskes/_shared/red-lines.md",
|
|
"success": true,
|
|
"data": {
|
|
"year": "<year>",
|
|
"clinic_uuid": null,
|
|
"month": "<month>",
|
|
"disabled_dates": "<dates>",
|
|
"enabled_dates": "<dates>",
|
|
"online_booking_enabled": true,
|
|
"booking_window": {
|
|
"value": 3,
|
|
"unit": "month"
|
|
}
|
|
}
|
|
}
|