Project feedback - Githubissues

Great work with last week's project! The complexity jump from week 2 to week 3 was significant, so it's understandable that you weren't able to cover all the stretch goals. Nonetheless, great job completing everything else!

Fundamentals

When working with any repository using git, always add a .gitignore file at the root folder of your project. This file can include any folders/files that shouldn't be added, like the .DS_Store file. You can read more here and find a template list of gitignores here
For the backend, even though it was simple in this case, having all routes and operations in a single file can make it difficult to read. For future projects, consider having a "routes" folder where each file groups routes related to specific functionality. Additionally, a "controller" folder can hold the logic to manipulate information, which is then called on the routes. You can read an example of this here
For the sortBoards functionallity, if you see you have some kind of same code in all you cases like the const data = await getBoards(); you could extract that at the beginning so it's more clear. Also, I noticed in this part of the code:
```
else if (sortOption === sortString) {
  const data = await getBoards();

  const sortedBoards = await data.filter(
    (board) => board.category == sortString
  );
  setBoards([...sortedBoards]);
}
```
I'm not sure I understand what's happening as the sortString is the input param, but in line 100 I see that the function is called with the sortOption being that param, so this should be always true, right? If that's the case should we make it the final else?
One of the advantages of using react is the ability to abstract html components, if you ever found yourself duplicating html code with just small set of changes, consider if it might be worth it to create a component for it. I thought about this while looking at top buttons code but still this might be not the case, but dumping my idea here for future cases.

Security

Same as last week, when adding any kind of keys into your projects don't publish them in public repositories. In this case I see that you used the .env file, but still you publish it into the repo. Add those files to the gitignore so they are not submitted. *Had offline discussion about this, and .env was added into the backends .gitignore but that doesn't cover the frontend directory, discussed what is the best approach about having a .gitignore in the root dir but still see the same point in fundamentals

Other

not 100% sure about this, but in the backend I think we could also gitignore the migrations folder within prisma as this is only the whole history of changes and if someone new needed to create the db they don't need the whole history but just create the new tables based on the latest version
I'm greatly surprised by all your design work when working on your projects! Still as projects grow and become more complex managing all design manually might not be scalable if you are working by yourself, so don't hesitate to use a css framework (list of css frameworks: https://github.com/troxler/awesome-css-frameworks) if designing becomes too time-consuming.
A common interaction is having the app name or logo in the header link to the homepage. Implementing this interaction would be beneficial.
When expecting longer input from users, like a full comment, it's a good idea to use a textarea

izuchukwumba / kudos-board

Project feedback #4