You are working on a App called "thisisatest" and your job is to review changes made.

Here is a high level description of "thisisatest":
```
The application is a simple ToDo app built using React. Its primary function is to allow users to manage a list of tasks (todos). Each task has a description and a state (open or completed, with the default state being open). The application is frontend-only, with no user sign-up or authentication process. The goal is to provide a straightforward and user-friendly interface for task management.

Features:
1. Display of Todos: A list that displays all todo items. Each item shows its description and a checkbox to indicate its state (open or completed).
2. Add New Todo: A button to add a new todo item. Clicking this button will prompt the user to enter a description for the new todo.
3. Toggle State: Each todo item includes a checkbox. Checking/unchecking this box toggles the todo's state between open and completed.
4. Local Storage: The application will use the browser's local storage to persist todos between sessions, ensuring that users do not lose their data upon reloading the application.

Functional Specification:
- Upon loading the application, it fetches existing todos from the local storage and displays them in a list.
- Each todo item in the list displays a checkbox and a description. The checkbox reflects the todo's current state (checked for completed, unchecked for open).
- When the user checks or unchecks a checkbox, the application updates the state of the corresponding todo item and saves the updated list to local storage.
- Clicking the "Add New Todo" button prompts the user to enter a description for the new todo. Upon confirmation, the application adds the new todo (with the default state of open) to the list and updates local storage.
- The application does not support deleting or editing todo items to keep the interface and interactions simple.
- Todos persist between sessions using the browser's local storage. The application saves any changes to the todo list (additions or state changes) in local storage and retrieves this data when the application is reloaded.

Technical Specification:
- Platform/Technologies: The application is a web application developed using React on frontend and Express on the backend, using SQLite as the database.
- Styling: Use Bootstrap 5 for a simple and functional interface. Load Boostrap from the CDN (don't install it locally):
    - https://cdn.jsdelivr.net/npm/bootstrap@5.0.2/dist/css/bootstrap.min.css
    - https://cdn.jsdelivr.net/npm/bootstrap@5.0.2/dist/js/bootstrap.bundle.min.js
- State Management: Directly in the React component
    - make sure to initialize the state from the local storage as default (... = useState(JSON.parse(localStorage.getItem('todos')) || []) to avoid race conditions
- Data Persistence: Using the SQLite database on the backend via a REST API.
```


Here are the technologies that should be used for this project:
* Node.js - JavaScript runtime needed to run the React development tools and build the project.

* react - A JavaScript library for building user interfaces.
* react-dom - Serves as the entry point to the DOM and server renderers for React.
* bootstrap - Frontend framework for developing responsive and mobile-first websites.

Here's what's already been implemented:

* React web app using Vite devserver/bundler
* Initial setup with Vite for fast development
* Basic project structure for React development
* Development server setup for hot reloading
* Minimal configuration to get started with React
* Frontend-only, compatible with any backend stack



Development process of this app was split into smaller tasks. Here is the list of all tasks:
```
1. Create a new component TodoList: This component will display the list of todo items. Use localStorage directly to access the current state of todos and map over them, rendering each todo item as a list item. Each item should display the todo's description and a checkbox that reflects the todo's state (checked for completed, unchecked for open). When the checkbox is clicked, dispatch an action to toggle the state of the todo. Also create AddTodo: This component will include a button that, when clicked, displays a prompt asking the user for a description of the new todo. Upon confirmation, dispatch an action to add the new todo to the state with a default state of open. Ensure the component also updates the local storage with the new list of todos. Finally, use TodoList and AddTodo components in App component to implement the required functionality. Integrate Boostrap 5 for styling - add CSS/JS to index.html, style App.jsx and other files as appropriate.
```

You are currently working on, and have to focus only on, this task:
```
Create a new component TodoList: This component will display the list of todo items. Use localStorage directly to access the current state of todos and map over them, rendering each todo item as a list item. Each item should display the todo's description and a checkbox that reflects the todo's state (checked for completed, unchecked for open). When the checkbox is clicked, dispatch an action to toggle the state of the todo. Also create AddTodo: This component will include a button that, when clicked, displays a prompt asking the user for a description of the new todo. Upon confirmation, dispatch an action to add the new todo to the state with a default state of open. Ensure the component also updates the local storage with the new list of todos. Finally, use TodoList and AddTodo components in App component to implement the required functionality. Integrate Boostrap 5 for styling - add CSS/JS to index.html, style App.jsx and other files as appropriate.
```

A part of the app is already finished.
These files are currently implemented in the project:
* `.eslintrc.cjs: Configuration file for ESLint, a static code analysis tool for identifying problematic patterns found in JavaScript code. It defines rules for linting JavaScript code with a focus on React applications.`
* `.gitignore: Specifies patterns to exclude files and directories from being tracked by Git version control system. It is used to prevent certain files from being committed to the repository.`
* `index.html: Main entry point for the project. It includes a basic HTML structure with a root div element and a script tag importing a JavaScript file named main.jsx using the module type. References: src/main.jsx`
* `package.json: Standard Nodejs package metadata file, specifies dependencies and start scripts. It also specifies that the project is a module.`
* `vite.config.js: Configuration file for Vite, a fast developer-friendly Javascript bundler/devserver.`
* `public/.gitkeep: Empty file`
* `src/App.css: Contains styling rules for the root element of the application, setting a maximum width, centering it on the page, adding padding, and aligning text to the center.`
* `src/App.jsx: Defines a functional component that serves as the root component in the project. The component is exported as the default export. References: src/App.css`
* `src/index.css: Defines styling rules for the root element, body, and h1 elements of a web page.`
* `src/main.jsx: Main entry point for a React application. It imports necessary modules, renders the main component 'App' inside a 'React.StrictMode' component, and mounts it to the root element in the HTML document. References: App.jsx, index.css`
* `src/assets/.gitkeep: Empty file`

Here are the complete contents of files relevant to this task:
---START_OF_FILES---
---END_OF_FILES---

Files that were modified during implementation of the task are:

Now I will show you how those files looked before this task implementation started. If a file is listed as the file that changed but is not in this list that means it was created during this task. Here are files before implementation of this task:

---start_of_files_at_start_of_task---
---end_of_files_at_start_of_task---

**IMPORTANT**
You have to review this task implementation. You are known to be very strict with your reviews and very good at noticing bugs but you don't mind minor changes like refactoring, adding or removing logs and so on. You think twice through all information given before giving any conclusions.

Each task goes through multiple reviews and you have to focus only on your part of review.
In this review, your goal is to check:
1. If there are some functionalities that were removed but are still needed.
2. If new files or functions are created but never called or used.
3. If there is some "dead code" that should be removed.
4. If there is some duplicate code resulting from refactoring or moving code into separate classes or files.

If everything is ok respond only with "DONE" and nothing else. Do NOT respond with thoughts, reasoning, explanations or anything similar if everything is ok, respond just with "DONE".

If you find any of these 4 mistakes, describe in detail what has to be changed.

**IMPORTANT**: Pay attention to file paths: if the command or argument is a file or folder from the project, use paths relative to the project root.
 For example:
 - use `dirname/filename.py` instead of `/path/to/project/dirname/filename.py`
 - use `filename.js` instead of `./filename.js`
All the steps will be executed in order in which you give them, so it is very important that you think about all steps before you start listing them. For example, you should never code something before you install dependencies or you should never try access a file before it exists in project.