Resolve all eslint errors

[LoTerence]

Overview

As a developer, we should resolve all eslint errors, so that the code maintains a high standard of quality and follows best practices, improving readability, consistency, and reducing the risk of bugs.

If you go into the frontend folder, and run npm run lint, 47 eslint errors and warnings come up.

Screenshot:

Action Items

• resolve all eslint errors

Resources/Instructions

Resources

[nooriaali9]

Hi @LoTerence this issue looks good, if it is currently being worked on, it can be moved to In progress.

[LoTerence]

@nooriaali9 I moved it to prioritized backlog.

Hey @irais-valenzuela if you are still working on this issue, could you move it to "In Progress" please? This is for PM stuff

[irais-valenzuela]

Hi @LoTerence, Thank you for writing up this ticket! I wanted to let you know that I'll be unassigning myself to avoid holding things up on your end. I have a few more interviews coming up, and I won’t have much time to dedicate to this.

[nooriaali9]

@irais-valenzuela Please update on this ticket - with the progress you've made on this!

[irais-valenzuela]

This ticket has been completed. I'm just waiting on code review for it to be merged. The PR is here

[LoTerence]

PR merged, thank you Ida!

There are still 16 eslint warnings left. I will make a new PR to clean up the rest.

[LoTerence]

Resolved with PR #640