To Do List
Keep a track of tasks you need to do.
An Application where you can keep a track of the tasks you need to do and checkout the ones that have already been completed.
Built With
- HTML
- CSS
- JavaScript
- Webpack
Live Demo
Getting Started
To get a local copy up and running follow these simple example steps.
Prerequisites
A Web Browser (preferably Google Chrome)
Setup
- Clone the GitHub Repository
- Go to the Project Directory
- Run
npm install
Usage
- Run
npm build
to build the project - Run
npm start
to start the live server
Authors
- GitHub: Awais Amjed
- Website: Coding Fries
- LinkedIn: LinkedIn
π€
Contributing
Contributions, issues, and feature requests are welcome!
Feel free to check the issues page.
Show your support
Give a
Acknowledgments
- Microverse
JavaScript best practices Check β
Keep all the JavaScript code in JS files, not in the script tag. β
Keep your Code Clean following this advice:
If you use node modules, .lock files should be in the repository to avoid problems with future versions of the dependencies. β
If you use ES6, use object destructuring to get the values from an object. This way you can avoid repeating a lot of code. β
Do not commit console.log to your repo. Itβs ugly, it kills performance and it can make confidential data be visible to anyone using the browser tools to look at your website. β
Do not use window.alert() or window.confirm(). Itβs ugly, impossible to style, stops code execution, and displays differently on different browsers. Use custom modal instead. β
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. β
Do not use document.write or eval β
Add node_modules dir to your .gitignore file as all those files are not needed in your repo (each team member will install all packages thanks to your package.json file). β
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. β
Peer-to-peer code review - M2W2
Great implementation. Regarding the specifications there is nothing to comment on.
Animations are nice, colors are pleasing and using Scss also was a good learning practice.
Great job.
Unit tests
In this Pull Request, We added the following unit tests:
In the second part of this Pull Request, We implemented the following unit tests:
Interactions
In this Pull Request, the following changes were implemented:
Live Demo Link
Crud functionality
In this Pull Request, the following changes were implemented:
Live Demo Link
List structure
In this Pull Request: