Add duration_days column, types, and multi-day date helpers#1085
Open
stefan-burke wants to merge 2 commits intomainfrom
Open
Add duration_days column, types, and multi-day date helpers#1085stefan-burke wants to merge 2 commits intomainfrom
stefan-burke wants to merge 2 commits intomainfrom
Conversation
Schema & types: - Add `duration_days INTEGER NOT NULL DEFAULT 1` to events table - Add `duration_days` to Event interface, EventInput, EventWithCount - Add `durationDays?` to EventBooking, BatchAvailabilityItem, UpdateEventLinkInput - Update testEvent factory and API example with the new field Date helpers: - Add `isRangeBookable`: checks every day in a multi-day range is bookable - Update `getAvailableDates`/`getNextBookableDate` to respect duration_days (excludes start dates whose full range would hit non-bookable days) Zero behavior change: all existing events have duration_days=1, which preserves single-day semantics throughout.
The schema hash auto-detects the column addition, but the human-readable version string should describe the latest structural change for debugging.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
duration_days INTEGER NOT NULL DEFAULT 1to events tableduration_daysto Event interface, EventInput, and type definitionsdurationDays?to EventBooking, BatchAvailabilityItem, UpdateEventLinkInputisRangeBookablehelper: validates every day in a multi-day range is bookablegetAvailableDates/getNextBookableDateto respect duration (excludes start dates whose full range would hit non-bookable days or extend past window)Zero behavior change: all existing events have
duration_days=1, which preserves single-day semantics throughout.PR Stack
duration-days/2-backend-engine— capacity engine + booking flow (depends on this)duration-days/3-admin-ui— admin UI + display (depends on Update bunny deploy script for build:edge #2)Test plan
test/lib/dates.test.tscover multi-day range exclusionGenerated by Claude Code