Good Job 👍 in implementing the ff. JavaScript Best Practices: 💯

• Keep all the JavaScript code in JS files, not in the script tag.
• Keep your code clean following this advice about:
• type checks === ✅
• descriptive variable and function naming ✅
• simplicity ✅
• the code is somewhat DRY but can still be improved ✅
• .lock files are included in the repository to avoid problems with future versions of the dependencies.
• Have used ES6 object destructuring to get the values from an object but can still be improved.

On the browser: 🌐

• No console.log found on the code
• No window.alert() or window.confirm() found on the code
• Keep the number of changes/updates to the DOM as low as possible, they are very expensive for the browser.
• Keep the application logic separated from DOM manipulation tasks.
• No document.write or eval
• Node_modules directory was added in the .gitignore file.
• No old pieces of code as inline comments

---

Cheers and Happy coding!👏👏👏

Feel free to leave any questions or comments in the PR thread if something is not 100% clear.

Good Job 👍 in implementing the ff. HTML & CSS Best Practices: 💯

• Use the appropriate tags for each element (e.g., links, titles, etc.) and use HTML5 semantic tags (e.g., header, nav) over divs.
• Avoid lines of code that are too long (100 characters or more).
• Be careful with blank lines and indentation.
• Do not add blank lines, spaces, or indentations without a reason.
• For readability, add blank lines to separate large or logical code blocks.
• For readability, add two spaces of indentation. Do not use the tab key.
• Close all HTML elements.
• Use lowercase for elements and attribute names.
• Always quote attribute values.
• Use space-less equal signs.
• Do not use inline styles. Keep your style definition in a separate CSS file.
• Do not overuse !important rule in your CSS style definitions.
• Always use the class attribute for multiple elements (do not use ID selector for multiple elements).
• If you want to create a CSS rule for multiple elements, use a class attribute instead.
• Do not commit old pieces of code as inline comments. They will make your project look messy. If you need to review a previous version of your code, you can always use git history.

---

Cheers and Happy coding!👏👏👏

Feel free to leave any questions or comments in the PR thread if something is not 100% clear.

Good Job 🎉 so far 💯

Here are some of the comments/suggestions found in the code: ♻️

• You can remove this line of code since when using the localStorage.setItem() it will automatically override the localStorage value with the same key.

https://github.com/mavericks-db/todo-list/blob/f035a845b1e0def2e75196ad0a297ea9ba3b6dee/src/modules/taskList.js#L89

---

Cheers and Happy coding!👏👏👏

Feel free to leave any questions or comments in the PR thread if something is not 100% clear.

Hi @mavericks-db,

Great job on creating a good looking to-do list 👍🏻 💯
✔️ Good styling.
✔️ Your to-do list's functionalities are smooth.
✔️ Your project has smooth interactions with the user ✨

Here are some of the improvements your team has suggested:

• We noticed that you use localStorage.clear() every time you want to override the existing entry in localStorage. The local storage overrides the existing entries automatically when you set a new value with the same key. So it's better to remove the localStorage.clear() lines to optimize your code.
• We noticed that some of your logic is split between multiple files. Please consider reconstructing your modules because index.js and status.js are almost empty and have no particular functionality.
• We suggest removing the e.preventDefault() on the input's event handler since it's not a form and it doesn't have an undesirable default behavior.