Skip to content

hooiyan/fem-todo-app

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

54 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

React Todo App

Table of contents

Overview

Summary

A dark/light themed React web app built together with Styled Components and Recoil that allows users to add, mark, and delete to-do items. The users can drag and drop to reorder the to-do items.

Links

Screenshot

Details

Project purpose and goal

One of my goals in becoming a front-end developer is to build at least one to-do app in my lifetime. This might be an overused project but I think it is a nice project for us to get hold of the basics of front-end development.

Web stack and explanation

At first, I planned to build this app with everything that I can do with just React (such as React state and CSS Modules) without installing external packages. However, I decided to integrate Recoil and Styled Components into the app.

React has always been my go-to framework for building web apps. I have heard of Recoil before and thought of giving it a try this time. I am glad that I chose it as the state management for this app. It is easy to get started with and I think it pairs with React very well.

Problem and thought process

CSS Modules is working well for me until I want to add theme switching capability. I think it is possible to realize that with CSS Modules. But I find it would be easier to use Styled Components in this case.

Most importantly, there's this one bug that had been bothering me for a day or two. I was not able to find the cause and I was frustrated. Luckily, I did find the cause when I was reviewing the map function that is used to loop over the todo items.

The problem is that whenever I delete a todo that is previously being checked off, which has a different styling from the one that has not been checking off yet, the styles will be applied to the next todo item. This is not what we want because the next item is supposed to have its original styling applied to it. So why does this happen? Well, it's because I did not give a unique value for the key props.

Lesson learned

  1. Previously, I have always been working on the main branch only. In this project, I tried to make use of git branching into my workflow. And it has helped me to not mess up with the main code. When I have to add something new to the project that might break the app, I create a new branch and continue working on that new feature.
  2. In React, we are required to provide a special props called key in each list item and it needs to be UNIQUE. I chose to provide index that we got from the map function. index does work in some cases, but we shouldn't rely on it because it does not guarantee the uniqueness.

Future improvements

  • Add animations when tasks are deleted
  • The ability to favorite a task and have it appear at the top of the list
  • The ability to create groups or categories of tasks
  • The ability to create a new user account

Useful resources

Getting started

These instructions will get you a copy of the project up and running on your local machine for development and testing purpose.

Installing

Clone the repository and run the development server:

npm install
npm start
# or
yarn install
yarn start

Contributing

Please feel free to send pull request if you want to contribute!

Author