How tham-bahadur-pun/issue-tracker works
Main Components
a. Frontend Layer:
• Issue Management UI (IssueChart, IssueSummary, LatestIssue)
• Navigation Components (Navbar)
• Issue CRUD Components (IssueForm, IssueDetail)
• Shared Components (ErrorMessage, Spinner, Pagination)
b. Next.js App Router Layer:
• Pages (/, /issues, /issues/[id], /issues/new)
• API Routes (/api/issues, /api/auth, /api/users)
• Layout System (layout.tsx, loading states)
c. Authentication Layer:
• NextAuth.js integration
• Auth Provider & Options
• Protected Routes
d. Data Layer:
• Prisma ORM
• Database Schema (Issues, Users)
• Database Migrations
e. External Services:
• Sentry (Error Tracking)
• Authentication Providers
Relationships and Data Flow
• Client-side requests → API Routes
• API Routes → Prisma Client
• Prisma Client → Database
• Authentication flow through NextAuth.js
• Error tracking flow to Sentry
Technical Stack Highlights
• Next.js 13+
• TypeScript
• Prisma ORM
• NextAuth.js
• Tailwind CSS
• Sentry
Key Design Patterns
Highlight:
• Component composition pattern
• Repository pattern (Prisma)
• Provider pattern (Auth, Query Client)
• Route handlers pattern
Important Notes:
• Keep the authentication flow visible but not overwhelming
• Separation between client and server components
• How error handling and loading states are managed
• Relationship between issues and users as shown in the Prisma schema