hey @billionsjoel ✋ while I was reviewing your codebase I found it well organized with best practice 🥇

but they are still some issues to work on to better improve it.

• on below line you should consider creating a list node and bind it to ul as best practice instead of overwriting string to ul 👍

https://github.com/billionsjoel/todo-app/blob/a85dd821a34b4ecfa0059cca0ff244f503058ffb/src/modules/RenderTask.js#L21

This PR suggests code reviews for the es6 awesome books app

• we suggest that you sort your array element in the sort function rather than having an entire module ex arr.sort((a,b) => a.index-b.index).
• we suggest that use forEach instead of map if you are just going to loop through the array.
• we suggest that you pass the todos array as a parameter instead of redeclaring it in each module.
• we suggest that you call the renderAllTasks method every time you update your array that way you can avoid having the renderTask method.

This PR adds and removes tasks with the interactive list actions

• Adding a new item.
• Removing a selected item.
• Marking a selected item as complete.
• Removing all items marked as complete at once.
• Add new JavaScript files and import it as a module:
• it will contain methods related to the status updates (completed: true / false).
• Add event listener to the checkbox (change).
• Update items object's value for completed key upon user actions.
• Implement a function for the "Clear all completed" button (use filter() method).
• Store the updated array of items in local storage, so the user gets the correct list values after the page reloads.

This PR creates tests for the todo list app.

• Create a test file ([..].test.js) for a file containing the add item and delete item functions that you want to test.

• Take a look at each of these functions. Are they pure functions? If the answer is "yes" then writing tests for them should be straightforward. Some of those functions however will update localStorage and manipulate the DOM. For those, you will need to use mocks:

• Mock a storage object to "imitate" localStorage operations (only if you are using jest < 24.x, in newer versions localStorage is mocked automatically).

• Mock HTML to test if add/delete functions add or remove exactly one

• element to/from the list in the DOM.

• Make sure you group your tests using the describe() method.

1. I can see code functionality works well but I would suggest using destructing for best practices.

2. Use classes to avoid variable repetitions so you can keep it DRY. I can see you are calling this variable almost in every file.

.

3. Good job on HTML and CSS good practices although I suggest that you avoid using the !important value as much as possible.

4. Good use of the compare module for sorting tasks although I suggest that you refactor and remove it because of YAGNI. You can sort within the sort function

This PR creates a todo list structure

• Set an array of some simple to do tasks (array of objects). Each task object contains three keys: 1. description [string]. 2. completed [bool]. 3. index: [number].

• A function to iterate over the tasks array and populate an HTML list item element for each task.

• On page load the list renders and the list appears in order of the index values for each task.

• All files in the dist are auto-generated by webpack.

This issue presents code reviews suggested on 25th-Jan-2022.

• We suggest you add the drag and drop feature to make the project complete. 😄
• We think it would be a good idea to move the test files to a test directory for modularity and a clean codebase.
• We also suggest that you fix the mobile version of the app. It looks like the app breaks on extra small devices.