How hyojinlee-git/banzzac-front works
Main Components
a. Core Application Layer:
• React + TypeScript Application (Vite-based)
• State Management (Recoil)
• Router (implied by pages structure)
b. Feature Modules:
• Authentication (Login/Signup)
• Profile Management
• Friends System
• Chat System (indicated by ChatMessageList component)
c. Technical Infrastructure:
• API Layer
• MSW (Mock Service Worker) for development
• Storybook for component documentation
UI Layer (Components)
↑↓
Feature Layer (Containers/Pages)
↑↓
State Management Layer (Recoil)
↑↓
Service Layer (API/Hooks)
↑↓
External Services
Specific Elements
a. Components Layer (Blue):
• Major component categories:
• Common Components (Button, Input, Modal, etc.)
• Feature-specific Components (ProfileImage, MatchingTicket, etc.)
• Layout Components
b. Feature Modules (Green):
• Friends Management
• Profile System
• Authentication
• Signup Flow
c. State Management (Purple):
• Recoil Stores:
• Common State
• Friends State
• Profile State
d. Service Layer (Orange):
• API Interceptor
• Custom Hooks
• MSW Integration
Important Relationships to Highlight
• Bidirectional data flow between Recoil stores and Features
• API communication patterns
• Component composition relationships
• Hook usage patterns
┌─ UI Layer ─────────────────────┐
• Components → Containers → Pages │
• Feature Layer ────────────────┤
• Friends │ Profile │ Auth │
• State Layer ─────────────────┤
• Recoil Stores │
• Service Layer ───────────────┤
• API │ Hooks │ MSW │
• ┘
Special Notes
• Modular structure reflected in the src/components organization
• Relationship between stories and components for documentation
• How the layouts system integrates with pages
• Demonstrate the hook system's role in managing side effects
Remember to highlight the TypeScript integration and how it provides type safety across the application layers. Also, note the development tools (MSW, Storybook) and how they fit into the development workflow.