[Frontend] Clean Error Message

[04mHuang]

To apply the ErrorMessage component, pass it the errors state. Errors should be named appropriately for display such as errors.lifeExpectancy for user's life expectancy since the string will be modified and used in the error message displayed to the user. Each error is a link that should be linked to an element's id. Use the same naming as before for the id e.g. id="lifeExpectancy".

To apply the styling, must import ErrorMessage.module.css and add a className to an element e.g. className={errors.initialLimit ? errorStyles.errorInput : ""} or errorStyles.highlight

[Copilot]

Copilot reviewed 11 out of 13 changed files in this pull request and generated 2 comments.

Files not reviewed (2)

• client/src/components/ErrorMessage.module.css: Language not supported
• client/src/index.css: Language not supported

Comments suppressed due to low confidence (1)

client/src/pages/scenarioSections/Investments.jsx:19

• The errors state is initialized as an array but later used as an object. Please initialize errors as {} to maintain type consistency and avoid runtime issues.

const [errors, setErrors] = useState([]);

[kalongn]

Is there any change into the middleware / type of error I need to check or is it another branch?

I just quickly run down create scenario and seems to be working okay. Did not read the code that closely

Also review Co-pilot suggestion