Issue: Implement Signup and Login Functionality (API Integration)

[sanjaysah101]

Issue: Implement Signup and Login Functionality (API Integration)

Description:

The UI for signup and login functionalities is complete. However, integration with the backend API to handle user registration, authentication, and session management is still required.

Desired Functionality:

• Signup: Users should be able to create new accounts by providing required information through the signup form. This data needs to be sent to the backend API for user registration.
• Login: Existing users should be able to log in using their credentials (e.g., email and password). Login credentials need to be validated against the backend API. Upon successful login, a user session should be established and relevant user data retrieved.
• Error Handling: Implement proper error handling for invalid user input, API errors, and other potential issues during signup and login attempts. Provide informative messages to the user.

API Integration:

• This issue focuses on integrating with the existing backend API for user management.
• Details regarding specific API endpoints, request/response formats, and authentication mechanisms should be documented elsewhere (link documentation if available).

[evnxprk]

Hello,

Would it be okay to work on this even though it's been assigned to you? I can try to help out if needed.

[sanjaysah101]

Hi @evnxprk,

Thank you for reaching out! I've made some progress on the Login Page functionality, with the login feature now operational. Currently, I'm planning to integrate the @legendState library for more efficient state management. However, there are still several outstanding tasks, such as implementing error message display for invalid input (like invalid email and password) directly within the input component. Additionally, updating the Input component to utilize the legend state (#16) is on my to-do list, and the SignUp form remains pending.

Given the interdependencies, addressing the error handling for issue #16 would be a great starting point, as it's currently blocking progress on this particular issue.

Looking forward to collaborating with you on this!