How matheusfcorocher/todo-app works
High-Level Architecture Overview
a. Core Layers (from inside out):
• Domain Layer (innermost)
• Application Layer
• Presentation Layer
• Infrastructure Layer (outermost)
Detailed Component Breakdown
Domain Layer:
• Domain repositories interfaces (TodoTaskCacheType)
Application Layer:
• AddTodoTask
• CompleteAllTodoTasks
• DeleteTodoTask
• UpdateTodoTaskState
• UpdateTodoTaskTitle
• DeleteAllCompletedTodoTasks
• IncompleteAllTodoTasks
Presentation Layer:
1. Controllers:
• TodoTaskController
• IsCompletedFilterController
2. View Models:
• TodoTaskViewModel
• FilterViewModel
3. Components (following Atomic Design):
• Atoms (Button, Checkbox, IconButton, TitleInput)
• Molecules (TodoFooter, TodoItem, TodoList, TodoMenu)
• Organisms (Todo)
Infrastructure Layer:
• Outermost ring containing:
• Cache implementation (TodoTaskCache)
• External dependencies (React, React-Spring, etc.)
Interaction Flows
• User interactions → View Components → Controllers
• Controllers → Use Cases → Domain
• Use Cases ← Domain Entities
• Infrastructure ↔ All Layers (dependencies)
Additional Elements
Specific sections for:
• Dependency Injection Container
• Testing Infrastructure
• Storybook Documentation
• Style System (CSS modules)
Technical Details
Annotations for:
• TypeScript compilation flow
• React component hierarchy
• Clean Architecture boundaries
• DDD patterns used