-
Notifications
You must be signed in to change notification settings - Fork 815
Description
❌ This issue is not open for contribution. Visit Contributing guidelines to learn about the contributing process and how to find suitable issues.
Original report by @pcenov
Observed while testing #13538
If I try to enroll a user to an already deleted class I am getting an unhandled error:
2025-07-10_11-47-27.mp4
Expected behavior
Should be further discussed.
Steps to reproduce the issue
- Install the build from BUM: Improved user creation #13538
- Go to Facility > Users and try to enroll a user in a class that has already been deleted
Usage Details
#13538
Windows 11, Ubuntu 22, Mac OS 15.5 - Chrome, Firefox
Acceptance criteria
The primary issue that we need to address critically is the way in which an error during form submission results in an unusable interface. The fix for this will be to ensure the user doesn't get stuck.
In general, this will apply to similar situations where the user's current state does not match the server-side state (eg, two users working simultaneously where one deletes a class just before another trying to assign/enroll users to the same class).
- Following Peter's steps to reproduce, identify and catch all errors coming back from the API. Then use the
handleApiError
function to display the API error page where they will be able to refresh and get new data.