https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41129
--- Comment #308 from Matt Blenkinsop <[email protected]> --- Created attachment 209504 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=209504&action=edit Bug 41129: (QA follow-up) End bookings on the due date - The latest bookable end was start + maxPeriod - 1, while the loan boundary marker and the max-period message used start + maxPeriod; the boundary landed on the first greyed-out day and that day reported a conflict instead of the max-period reason - Checking out a booking sets the due date to the booking end, and a checkout on the start date is due on start + issuelength, which is also what place_booking.js allowed; end bookings there - calculateMaxEndDate returns start + maxPeriod, and the end-date-only forced end, the range preview and the max-period message all use it - Pin that the loan boundary is the last selectable end and that the max-period message starts the day after - Restore the DatePicker spec's original max-date expectation Test plan: 1. Set issuelength 3 with no renewals and open the booking modal 2. Pick a start date S with nothing around it 3. Confirm S+1 to S+3 are selectable, S+3 carries the loan boundary marker, and hovering S+4 reports the maximum booking period 4. Run: yarn cypress run --component --spec "t/cypress/component/lib/booking/**/*_spec.ts,t/cypress/component/useBookingCalendarMaps_spec.ts" 5. Run: yarn cypress run --spec t/cypress/integration/Circulation/bookingsModalDatePicker_spec.ts 6. Confirm both pass Assisted-by: Opus 5.5 (Anthropic) Signed-off-by: Paul Derscheid <[email protected]> Signed-off-by: Matt Blenkinsop <[email protected]> -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list -- [email protected] To unsubscribe send an email to [email protected] website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
