Frontend form error handling

[Yasoop]

Description

Redirects to a different page if the review form is unsuccesful. Toast popup happens when exiting to home page.

Motivation and Context

Handles backend review form error.
Closes #114

How has this been tested?

Tested errors by putting more than 2 reviews in one cycle and submitting more than 5 reviews total

Screenshots (if appropriate):

If there are more than two reviews in a cycle or more than 5 reviews are submitted, then the submit button on the last page of the form is clicked, redirects to this page.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• [ x] New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• My code follows the code style of this project.
• I have moved the ticket to "In Review"
• I have added reviewers to this PR
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
cooper	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 20, 2025 11:20pm
cooper-auth	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 20, 2025 11:20pm
cooper-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 20, 2025 11:20pm

[banushi-a]

This is a good start so far. I think we should also try and do some error handling earlier in the form as well. Check the updated ticket for the new requirements which I think make the user experience better.

[banushi-a]

small requested changes, great progress

[banushi-a]

I think I figured out how we can stop them before they get too far:

If you look at the screenshot below, I added a check in the next function to make sure that they aren't submitting too many reviews. The way we do this is fetch all of the users reviews once they open the form, this way we have them loaded in memory. Once they are on the cycle page, they can enter any term, but if they already did 2 reviews, they will be stopped!

Since most of the boilerplate is there, try and see if you can implement the logic in the //Todo on your own @Yasoop !

(also remove the console.log lol)

[banushi-a]

For the formatting @Yasoop @suxls if you have prettier installed as a vscode extension you should be able to just save the file and it reformats. If this doesn't work for you follow this quick guide: https://www.digitalocean.com/community/tutorials/how-to-format-code-with-prettier-in-visual-studio-code

[banushi-a]

lfg