You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2020. It is now read-only.
Throughout Reservations, if you press a button twice, or many times before the page loads, it sends the action consecutively. This can lead to multiple reservations being created (when the button is the confirm reservation button). Or, if the button is the confirm equipment checkout, it leads to multiple check-outs on the Notes (see SS). Another instance is creating an equipment item.
So far, there doesn't seem to be any large undoable damage that this bug can cause, but it would be best if we could resolve by making sure multiple consecutive actions aren't executed, and only the most recent one is.
I'm not sure how to implement this, or if this is just a byproduct of the fact that each action just triggers a route and there is nothing we can do.
The text was updated successfully, but these errors were encountered:
Throughout Reservations, if you press a button twice, or many times before the page loads, it sends the action consecutively. This can lead to multiple reservations being created (when the button is the confirm reservation button). Or, if the button is the confirm equipment checkout, it leads to multiple check-outs on the Notes (see SS). Another instance is creating an equipment item.
So far, there doesn't seem to be any large undoable damage that this bug can cause, but it would be best if we could resolve by making sure multiple consecutive actions aren't executed, and only the most recent one is.
I'm not sure how to implement this, or if this is just a byproduct of the fact that each action just triggers a route and there is nothing we can do.
The text was updated successfully, but these errors were encountered: