Test: Client and Server: Input checks before data sent to server and server check input legitimate

[nikobatzi1990]

Write some tests to check that the input values are legitimate before adding them to the database (i.e., check that the Email input is actually an email address instead of random letters). #112 #114 #113

All of the fields should be filled in before submission (no leaving Nickname empty, for example). #95

[SirrorsMoore1975]

[Refactored Comment]
Client Side:

1. Username: characters that cannot be used, must not existed 255 characters (or much lesser) and cannot be empty Feat: Nickname or username cannot be empty #114
2. Email: required domain name, dot co or dot com, email's name, all character must be in lowercase and no special characters, Feat: Check email validity at client level #112
3. Dropdown menu: alert user when user did not select any company brand, ie. companyName !== ""　<-- (EDIT) 20231128 Future me: When user click the review button at the provider page, the user would be expecting the review is for that phone provider
4. Add an alert window to confirm user choices / alert user with error(s) on screen Feature: Review Form: Warn users and provide final confirmation to review #95

Server Side:
Taiga's team seems to have implement some test on checking the validity of email, whether input fields are empty or whether the score is a Number.

[TaylorC19]

Add checks within the /api/review post endpoint.
These test should
-check that the email is in an email format (could also use type='email' in the input component).
-check the score numbers are valid
-profanity filter for reviews/names

if review is invalid, return falsey statement