Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Borrow: wrong availability displayed, when model is already in a expired basket of the user #1711

Open
neoheat opened this issue Apr 10, 2024 · 0 comments

Comments

@neoheat
Copy link
Collaborator

neoheat commented Apr 10, 2024

Application
borrow

Describe the bug

Prerequisits:
A model (which has availability 1) is already in an expired shopping cart with a certain date range.

The user adds the same model (as already in the expired basket) with a date range, that overlaps the above dates. The availability calendar of the model does show an availability of 1, despite there is already the same model in the users basket.

To Reproduce

  1. Search for a model which has an available amount of 1 item (e.g. 59c8d2b0-3717-5317-ba1d-de09206c42d2)
  2. Make a reservation for this item by adding it to the basket, choose a date range (2 days, Wednesday–Thurday)
  3. Wait until the basket expires (30')
  4. Search for the same model as before and add this model to the basket, choose a date range in the same week as before, but from Monday-Friday (time range must be overlapping, but not exactly the same)

--> see wrong availability in the availability calendar

Expected behavior
By click on button "Add Item":

  • the expired basket shall be "reactivated"
  • the same model as already placed in an expired basket, shall display the correct availability in the availability calendar

Screenshots

Image
Image

Desktop (please complete the following information):

  • Device: Desktop, Mobile
  • OS & Version: any
  • Browser & Version any

Additional context
Relates to #1708

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Ready to start
Development

No branches or pull requests

1 participant