v0.1.1-beta

📋 Simple Educational To-Do App v0.1.1-beta

Overview

This release includes a major backend refactoring, with routes now organized into a separate routers directory. Also added the Ruff linter for improved code quality. The frontend now features a spinner during task deletion and supports task reordering using Framer Motion's Reorder component, enhancing the user experience with drag-and-drop functionality.

New features

• Integration of Ruff linter.
• Backend refactoring with separate routers directory.
• Spinner added during task deletion.
• Task reordering using Framer Motion's Reorder component.
• New screenshots directory to capture UI changes by version.

---

📂 Project Structure

    todo-app/
    │
    ├── backend/
    │   ├── __init__.py
    │   ├── main.py
    │   ├── models.py
    │   ├── initialize_db.py
    ├── routers/
    │   ├── create_task.py
    │   ├── delete_task.py
    │   ├── read_tasks.py
    │   ├── reorder.py
    │   ├── update_task.py
    │   └── __init__.py
    │   ├── schemas/
    │   │   ├── reorder_request.py
    │   │   └── task.py
    │   └── requirements.txt
    │
    ├── frontend/
    │   ├── src/
    │   │   ├── components/
    │   │   ├── pages/
    │   │   ├── App.tsx
    │   │   ├── main.tsx
    │   │   └── ...
    │   ├── index.html
    │   ├── package.json
    │   ├── vite.config.ts
    │   └── ...
    │
    ├── screenshots
    │
    └── README.md

Future Enhancements 🌟

The following features are planned for future releases:

• onDelete: add spinner loading.
• Ruff: Integrate a linter to maintain code quality.
• Mypy: Add static type checking to ensure code reliability and correctness.
• Docker: Set up CI/CD.
• New Design: Update the UI to a more advanced version with animation.
• Edit Task: Allow users to edit the description of existing tasks.
• Reorder Tasks: Enable users to change the order of tasks in the list.
• Framer Motion: Exit animation for list's Task

What's Changed

• add: Spinner component by @e-Nicko in #1
• chore: add sass by @e-Nicko in #2
• chore: styles for .Task by @e-Nicko in #3
• chore: styles correction by @e-Nicko in #4

Full Changelog: v0.1.0-beta...v0.1.1-beta

v0.1.0-beta

🎉📋 Simple Educational To-Do App v0.1.0-beta

Overview

This is the most basic and fundamental realization of an educational to-do app project. The primary goal of this release is to provide a simple, functional example of a to-do application that allows users to add, delete, and mark tasks as complete. The frontend design is intentionally kept minimal with basic CSS styles to ensure clarity and ease of understanding for educational purposes.

Functionalities ⚙️

1. Add New Task ➕

• Users can add new tasks to the to-do list. This functionality allows users to enter a task description and add it to the list.

2. Delete Task ❌

• Users can delete tasks from the to-do list. Each task has a delete button that allows users to remove it from the list.

3. Mark Task as Complete ✔️

• Users can mark tasks as complete. This functionality allows users to check off tasks from the list, indicating they have been completed.

---

Design 🎨

The frontend design is minimalistic, focusing on functionality over aesthetics. The CSS styles are simple, ensuring that users can easily follow along and understand the structure and behavior of the application.

Limitations 🚫

• No Edit Function: Users cannot edit existing tasks. This functionality will be introduced in future releases.
• No Task Reordering: Users cannot change the order of tasks. This will also be included in future updates.

Future Enhancements 🌟

The following features are planned for future releases:

• Ruff: Integrate a linter to maintain code quality.
• Mypy: Add static type checking to ensure code reliability and correctness.
• Docker: Set up CI/CD.
• New Design: Update the UI to a more advanced version with animation.
• Edit Task: Allow users to edit the description of existing tasks.
• Reorder Tasks: Enable users to change the order of tasks in the list.
• Spinner Loading: Add a loading spinner when fetching data to improve user experience during asynchronous operations.