How caturhidayat/issue-tracker works
Main System Components
a) Frontend Layer:
• Next.js App Router architecture (indicated by the /app directory)
• Client Components (components directory)
• Server Components (pages)
• Server Actions (actions directory)
b) API Layer:
• REST API endpoints (api directory)
• Route handlers for CRUD operations
c) Database Layer:
• Prisma ORM
• Underlying database (likely PostgreSQL based on Prisma setup)
┌─────────────────────────────────────────┐
• Client Layer │
• ┌─────────────┐ ┌─────────────────────┐ │
• Components │ │ Pages │ │
• Navbar │ │ - Home (page.tsx) │ │
• ListIssues│ │ - Issue (issue/*.tsx)│ │
• ┘ └─────────────────────┘ │
• ┘
┌─────────────────────────────────────────┐
• Server Layer │
• ┌─────────────┐ ┌─────────────────────┐ │
• API Routes │ │ Server Actions │ │
• /api/issue │ │ /actions/issue │ │
• ┘ └─────────────────────┘ │
• ┘
┌─────────────────────────────────────────┐
• Data Layer │
• ┌─────────────┐ │
• Prisma ORM │ │
• Database │ │
• ┘ │
• ┘
Technology Stack Callouts
• Next.js 13+ (App Router)
• Prisma ORM
• TypeScript
• Tailwind CSS
• Database system
Component Relationships
Specific interactions:
• FormIssue → Server Actions
• ListIssues → API Routes
• EditIssueDialog → Server Actions
• DeleteButton → API Routes
Data Flow Patterns
Patterns:
• Server-side rendering flow
• Client-side mutations
• API route handling
• Database queries through Prisma
Use different line styles to represent:
Environment Configuration
A small section showing:
• Development environment setup
• Environment variables flow
• Build/deployment configuration