Todolist 📓

This project was generated with Angular CLI version 13.3.6.

Live at: https://to-do-list-angular-nu.vercel.app/

Development server 📖

Run ng serve for a dev server. Navigate to http://localhost:4200/. The application will automatically reload if you change any of the source files.

Code scaffolding 📖

Run ng generate component component-name to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module.

Build 📔

Run ng build to build the project. The build artifacts will be stored in the dist/ directory.

Running unit tests

Run ng test to execute the unit tests via Karma.

Running end-to-end tests

Run ng e2e to execute the end-to-end tests via a platform of your choice. To use this command, you need to first add a package that implements end-to-end testing capabilities.

Further help

To get more help on the Angular CLI use ng help or go check out the Angular CLI Overview and Command Reference page.

Project context

Normally, we use applications to write down tasks that we have to do during projects. This time, instead of using an external application, we will do our own. Also, we will need to store those tasks to check which ones have been completed throughout the week.

Estimated time: 1 sprint of 1 week

ScreenShot

Functional requirements:

• New tasks can be added.
• Tasks can be checked (it changes color).
• Tasks can be deleted.
• Tasks can be edited (by double clicking).
• A button that displays a popup window with the finished tasks and the deleted tasks.
• Extra:
  • As a plus, a button where tasks can be filtered.

Non-functional requirements:

• The web must be in deploy, even if it is under development.
• GitFlow is required.

💻 Technologies

• Git / Github
• Vercel
• JavaScript
• TypeScript
• Angular

💼 Deliverables

• Readme
• GitHub Page o Heroku
• Url en ‘deploy’

Contexto del proyecto

Normalmente, usamos aplicaciones para apuntar tareas que tenemos que hacer durante los proyectos. Esta vez, en vez de utilizar una aplicación externa, haremos la nuestra. Además, necesitaremos almacenar esas tareas para verificar cuáles se han completado a lo largo de la semana.

Tiempo estimado: 1 sprint de 1 semana

Requisitos funcionales:

• Se pueden agregar tareas nuevas.

• Se puede dar check a las tareas (esta cambia de color).

• Se pueden eliminar tareas.

• Se pueden editar tareas (al dar doble click).

• Un botón que despliegue una venta emergente con las tareas terminadas y las tareas eliminadas.

• Extra:

  • Como plus, un botón donde se puedan filtrar las tareas.

Requisitos no funcionales:

• La web deberá estar en deploy, aunque esté en desarrollo.
• Se requiere usar GitFlow.

💻 Tecnologías

• Git / Github
• Heroku
• JavaScript
• TypeScript
• Angular

💼 Entregables

• Readme
• GitHub Page o Heroku
• Url en ‘deploy’