-
Notifications
You must be signed in to change notification settings - Fork 57
Calendar availability incorrect #1218
Comments
Note that when I tried to create a reservation starting on the due date |
Another note: manually editing the second reservation to start on the due date of the first fixes the calendar issue but not the renewal issue. |
Ok, so I've figured part of this out. The |
Verified - a reservation is no longer |
Resolves #416 - add tests for Reservation actions (creation, equipment handling, renewal) - add tests for Rails Admin routes - resolve issue with renewals (see #1218) - add numerous helpers for integration tests - misc cleanup of other tests - resolve deprecation warning reintroduced by #1081 - clean up tests from #987
Confirmed, you can renew an overdue reservation. I'm going to make the fix in the #416 branch and focus on the JS weirdness. |
Resolves #416 - add tests for Reservation actions (creation, equipment handling, renewal) - add tests for Rails Admin routes - resolve issues with renewals (see #1218) - add numerous helpers for integration tests - misc cleanup of other tests - resolve deprecation warning reintroduced by #1081 - clean up tests from #987
Apparently we had a test specifying that overdue reservations should be eligible for renewal, which makes no sense to me. We'll fix that :-) |
Resolves #416 - add tests for Reservation actions (creation, equipment handling, renewal) - add tests for Rails Admin routes - resolve issues with renewals and add specs (see #1218) - add numerous helpers for integration tests - misc cleanup of other tests - resolve deprecation warning reintroduced by #1081 - clean up tests from #987
Resolves #416 - add tests for Reservation actions (creation, equipment handling, renewal) - add tests for Rails Admin routes - resolve issues with renewals and add specs (see #1218) - add numerous helpers for integration tests - misc cleanup of other tests - resolve deprecation warning reintroduced by #1081 - clean up tests from #987
Resolves #416 - add tests for Reservation actions (creation, equipment handling, renewal) - add tests for Rails Admin routes - resolve issue with renewals (see #1218) - add numerous helpers for integration tests - misc cleanup of other tests - resolve deprecation warning reintroduced by #1081 - clean up tests from #987
Resolves #416 - add tests for Reservation actions (creation, equipment handling, renewal) - add tests for Rails Admin routes - resolve issues with renewals and add specs (see #1218) - add numerous helpers for integration tests - misc cleanup of other tests - resolve deprecation warning reintroduced by #1081 - clean up tests from #987 - refactored the for_eq_model Reservation scope not to call .finalized
Fixed the JS weirdness, it's always the freaking time zones 😠! Thankfully @squidgetx wrote a |
Resolves #1218 - use dateInTimeZone instead of new Date for consistency
It's a problem with our current system because then those overdue "days" are lost from record, but I don't see a higher level conceptual reason why overdue equipment should be ineligible for renewal. The way a lot of libraries work is that they keep track of how many overdue days a book has. If you renew an overdue book your fine stops increasing, but you still have to pay it. |
And then you'd rely on the other equipment availability / reservation length / renewal validations to restrict the ultimate reservation length? I'm not sure I like that since then you could just remain overdue for a while, and then "renew" at the end to get some extra free days even if it's beyond the usually acceptable length. Someone with an overdue reservation should be encouraged to return it ASAP, not given the option to just keep it. If they want to bring it back and immediately re-reserve it at the counter to end their overdue reservation but keep the equipment that's fine, but I don't think they should be given the option to keep the equipment for free once they've gone past the due date without coming in to the office (it's not like they don't get a reminder e-mail). |
Resolves #416 - add tests for Reservation actions (creation, equipment handling, renewal) - add tests for Rails Admin routes - resolve issues with renewals and add specs (see #1218) - add numerous helpers for integration tests - misc cleanup of other tests - resolve deprecation warning reintroduced by #1081 - clean up tests from #987 - refactored the for_eq_model Reservation scope not to call .finalized
Ah, you're right. Most library systems have a key "hold" feature that I forgot about that makes this more economical: other patrons can put an item on hold. Then no one can renew it. That itself might be a worthwhile future feature though. For now, we should probably not allow overdue renewals. |
Well that's basically what our "reservations" are, right? 😛 |
This issue relates to the broken calendar view noted below; the issues with renewals were fixed in the #416 branch.
While writing tests for renewals for #416 I came across a weird bug. The calendar / Reservations doesn't consider the equipment occupied on the due date, and neither does the renewal code. Steps to replicate:
Time.zone.today
untilTime.zone.today + 1.day
(for equipment model with a single equipment item)Time.zone.today + 2.days
untilTime.zone.today + 3.days
Time.zone.today + 4.days
in the calendarThis might be resolved in #462, or it might not 😛.
Screenshots
The text was updated successfully, but these errors were encountered: