Update and store the email sent ID and its current status in the user database. Additionally, we need to update the web app route /emails to display a list of emails sent by the user account.
Pre-Condition
Implemented email sending route in API.
Login implementation finished.
Tasks
Develop the Emails page:
Set up a new route in the Remix project for /emails.
Create a page with the following components:
Table list of sent emails (fetched from the user database)
Status of each email
Fetch and display sent emails:
Fetch the list of sent emails from the user database.
Display the email ID and current status for each email.
Update email sending logic:
On email submission, store the email ID and its status in the user database.
Ensure the status is updated appropriately based on the email sending process.
Handle email status updates:
Implement logic to update the status of emails in the database.
Additional Context
Ensure the page is styled consistently with the rest of the web app.
Provide appropriate error handling for the fetch call and form submission.
Labels
frontend, enhancement, authentication
Acceptance Criteria
[ ] Only logged-in users can access the /emails route.
[ ] The Emails page contains a title and a small description.
[ ] A list of sent emails is fetched and displayed.
[ ] Each email's ID and current status are displayed.
[ ] On email submission, the email ID and status are stored in the user database.
Description
Update and store the email sent ID and its current status in the user database. Additionally, we need to update the web app route
/emails
to display a list of emails sent by the user account.Pre-Condition
Tasks
Develop the Emails page:
/emails
.Fetch and display sent emails:
Update email sending logic:
Handle email status updates:
Additional Context
Labels
frontend
,enhancement
,authentication
Acceptance Criteria
/emails
route.