Description:
The backend validation already prevents appointment creation for non-existent users, but the UI currently only logs the error in the console:
book-appointment-form.component.ts:309 Email is not associated with an existing account.
There is no visible feedback for the admin in the form. This can cause confusion because the form simply appears to fail silently.
Expected Behavior:
-
When an admin enters an email not linked to an existing account and submits the form, a visible UI marker should be shown.
-
This should be a warning/failure notification (e.g., toast, alert, or inline form error) clearly stating:
"The email you provided does not correspond to an existing account.”
Acceptance Criteria:
- Notification is displayed when validation fails due to non-existent email.
- Admin can immediately understand why the appointment could not be created.
- Error remains visible until dismissed or corrected.
Notes:
- Functionality is already solved on the backend.
- This issue is only for improving UI/UX feedback.
Labels: UI/UX, bug, enhancement
Description:
The backend validation already prevents appointment creation for non-existent users, but the UI currently only logs the error in the console:
book-appointment-form.component.ts:309 Email is not associated with an existing account.There is no visible feedback for the admin in the form. This can cause confusion because the form simply appears to fail silently.
Expected Behavior:
When an admin enters an email not linked to an existing account and submits the form, a visible UI marker should be shown.
This should be a warning/failure notification (e.g., toast, alert, or inline form error) clearly stating:
Acceptance Criteria:
Notes:
Labels: UI/UX, bug, enhancement