Improve form validation and error handling across the HEALCONNECT application.

[Adithyakp86]

🐛 Issue Description

Improve form validation and error handling across the HEALCONNECT application.

Currently, some forms do not provide clear validation messages when users enter invalid or incomplete information. This can lead to confusion and poor user experience.

🎯 Proposed Solution

• Add proper validation for all required form fields.
• Display clear and user-friendly error messages.
• Validate email, phone number, password, and other relevant fields.
• Prevent form submission when required fields are invalid.
• Display success messages after successful form submission.
• Handle API/Firebase errors gracefully.
• Maintain consistent validation and error-message styling across the application.

✅ Expected Behavior

Users should receive immediate and understandable feedback when they enter invalid data.

For example:

• Please enter a valid email address.
• Phone number must contain 10 digits.
• Password must be at least 8 characters.
• This field is required.

After successful submission:

• Form submitted successfully.

📌 Acceptance Criteria

• Required fields are properly validated.
• Email validation is implemented.
• Phone number validation is implemented.
• Password validation is implemented where applicable.
• Appropriate error messages are displayed.
• Invalid forms cannot be submitted.
• Firebase/API errors are handled properly.
• Success messages are displayed after successful submission.
• Validation behavior is consistent across the application.
• Existing functionality is not broken.

💡 Additional Notes

The implementation should follow the existing project structure and UI design. Validation should be user-friendly and should not negatively affect the existing application functionality.

[github-actions]

Thank you for raising this issue!

We'll review it as soon as possible. We truly appreciate your contributions! ✨

Meanwhile make sure you've visited the README.md, CONTRIBUTING.md, and CODE_OF_CONDUCT.md before creating a PR for this. Also, please do NOT create a PR until this issue has been assigned to you. 😊

[github-actions]

Thanks for opening this issue! 🚀

Please adhere to Apertre'26 Rules:

1. Do NOT create a PR until this issue is assigned to you.
2. Include apertre3.0 tag.
3. Provide ONE Difficulty Tag (easy / medium / hard).
4. Include screenshots if it's UI-related.

A mentor will review and assign this issue soon.