Stefan Lazic
9f981173f4
CI / ci (push) Canceled after 0s
The owner page Where: Manage → Business → Holidays, at /owner/settings/holidays. It needs the same permission as Business Details. Adding: you enter a name, a start date and an optional end date. Leaving the end empty gives a single day. Upcoming and past: upcoming holidays are listed by date, with a trash icon to remove each one. Past ones sit in a collapsed “Past” list. Existing bookings: if appointments are already booked on those dates, you see them and confirm with “Add Anyway”, the same pattern as Opening Hours. Nothing is cancelled automatically. What it does to booking Customer calendar: holiday dates are greyed out, for every staff member and every service. Time slots: no slots are offered on those dates. Direct bookings: staff and owner bookings and reschedules onto a holiday are refused, with a message naming the holiday. This is deliberate, but if you want owners to be able to override it, that’s a small change.
17 lines
655 B
SQL
17 lines
655 B
SQL
-- CreateTable
|
|
CREATE TABLE `BusinessHoliday` (
|
|
`id` VARCHAR(191) NOT NULL,
|
|
`businessId` VARCHAR(191) NOT NULL,
|
|
`name` VARCHAR(191) NOT NULL,
|
|
`startDate` DATE NOT NULL,
|
|
`endDate` DATE NOT NULL,
|
|
`createdAt` DATETIME(3) NOT NULL DEFAULT CURRENT_TIMESTAMP(3),
|
|
|
|
INDEX `BusinessHoliday_businessId_startDate_endDate_idx`(`businessId`, `startDate`, `endDate`),
|
|
PRIMARY KEY (`id`)
|
|
) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci;
|
|
|
|
-- AddForeignKey
|
|
ALTER TABLE `BusinessHoliday` ADD CONSTRAINT `BusinessHoliday_businessId_fkey` FOREIGN KEY (`businessId`) REFERENCES `Business`(`id`) ON DELETE CASCADE ON UPDATE CASCADE;
|
|
|