Skip to content

Conversation

@kostiantynkovalchuk
Copy link

No description provided.

Copy link
Collaborator

@aniolg aniolg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @kostiantynkovalchuk 👋,

Thanks for submitting your PR! Looks really well, and you applied right all the concepts of the last class. 🥇

If you want to improve it, you can try to apply the colors on the status badge or set icons on date/designers cells, to being more accurate on the Figma example.

See you in the next class!

Keep going strong 👍

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

.vscode/ is a directory created by the VS Code application to store configurations. In that case, is keeping the settings at repository level. So in general, it's something you would rather not include in your public repository.

Could be better to add .vscode/ directory to .gitignore file on this repository.

(FYI: .gitignore is a file located in the root of the repo, where you can specify which files or directories want to be ignored by git when you do your commits.)

💡 You can find how to do it in the GitHub documentation.

<ul>
{taskItems.map((task, index) => (
<TaskItem
key={index}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would recommend that you not use only the index as key when you are rendering a list on React because if in the future you will edit that list, you can create confusing errors.

ℹ️ You can find deeply explanation on the Rendering List article of Rect documentation

✨ Tip: In an ideal scenario, in the data of your item, you will have a unique id/sku/... that you can use as a key. If this is not your case, you can concatenate the index with a probably unique value of your data (like the name), like the below example:

@kostiantynkovalchuk
Copy link
Author

kostiantynkovalchuk commented Feb 8, 2025 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants