Describe the bug
Using the client side of the application, I can select some shifts that overlap in time (user error) and proceed with the sign up process. The server correctly identifies the problem and only signs me up for one of the shifts, rejecting overlapping shifts and returning an error code 409. However, from the client side, it looks as if the sign-up was successful. See screenshots below.
I select overlapping times:
I submit the request and get this screen, making me think that I signed up for 2 shifts at different shelters:
When I look at my upcoming shifts, I see only one shift (which is correct, because the server only signed me up for one shift):
To Reproduce
Steps to reproduce the behavior:
Go to "Sign Up for Shifts"
Sign up for two shifts in different shelters with the same start and end times
Click on Submit Shifts, you'll see the screen that makes you think that you signed up for both shifts
Go to "Upcoming Shifts" and you'll see that you only signed up for one shift
Expected behavior
On step 3 above, the confirmation screen should somehow indicate which shifts were successfully created and which were not.
Describe the bug Using the client side of the application, I can select some shifts that overlap in time (user error) and proceed with the sign up process. The server correctly identifies the problem and only signs me up for one of the shifts, rejecting overlapping shifts and returning an error code 409. However, from the client side, it looks as if the sign-up was successful. See screenshots below.
I select overlapping times:
I submit the request and get this screen, making me think that I signed up for 2 shifts at different shelters:
When I look at my upcoming shifts, I see only one shift (which is correct, because the server only signed me up for one shift):
To Reproduce Steps to reproduce the behavior:
Expected behavior On step 3 above, the confirmation screen should somehow indicate which shifts were successfully created and which were not.