feat: develop complete retro

[nishadipri]

Description

Uploading Screen Recording 2024-04-28 at 07.18.18.mov…

Fixes # (issue)

How to test?

Please provide a short summary how your changes can be tested?

Checklist

• I have performed a self-review of my own code
• I have followed the name conventions for CSS Classnames and filenames, Components names and filenames, Style filenames, if you are in doubt check the the project README.MD and here https://github.com/HackYourFuture-CPH/curriculum/blob/master/review/review-checklist.md
• I have commented my code, particularly in hard-to-understand areas, if you code was simple enough mark the box anyway
• I have made corresponding changes to the documentation, if you code was simple enough mark the box anyway
• This PR is ready to be merged and not breaking any other functionality

[orhantoy]

I used ChatGPT to propose a better way of doing this query:

const getTeamMembers = async (params) => {
  const { teamId } = params;

  // Using Knex's query builder to construct the SQL query
  const results = await knex('Employees')
    .select('Employees.first_name', 'Employees.last_name', 'TeamMembers.id')
    .join('TeamMembers', 'TeamMembers.employee_id', '=', 'Employees.id')
    .where('TeamMembers.team_id', Number(teamId));  // Safely parameterized

  return {
    teamMembers: results[0],
  };
};

Try it out and see if it works.

[nishadipri]

I have tried this. But it's given me some errors.

[orhantoy]

Any special reason for having this as a function instead of doing a map inside the <select> further down?

[nishadipri]

Separated the mapping logic as its own function because it's easy to read and clear.

[komalranjan9]

@nishadipri I am going to merge to main, as you asked.