How hemanthvsp1/kanban_task_board works
Task Board is a React Kanban app for personal and shared team workspaces. A user enters the board, authenticates (including guest access), then creates and manages tasks, moves them across statuses, and uses assignments, labels, comments, activity, search, filters, and summary stats. The frontend accesses Supabase directly by default or can route supported requests through the optional Go API. Supabase Postgres and RLS persist and protect the data; the API verifies JWTs and runs queries in RLS-scoped transactions. The frontend excerpt is partial, so the documented capabilities are shown without inferring their individual call wiring.
Main entry points: App.tsx Board experience · main.go Go API router · pool.go RLS query pool · supabase.ts Authenticated API client
Components 16
Task Board UI
- React entry
src/main.tsx - Board experience
src/App.tsx - Authenticated API client
src/lib/supabase.ts
Supabase Services
- Supabase client
src/lib/supabase.ts - Supabase Auth
- Board realtime
Optional Go API
- Go API router
server/main.go - JWT and CORS middleware
server/middleware/auth.go - Task operations
server/handlers/tasks.go - Task comments
server/handlers/comments.go - Task activity
server/handlers/activity.go - Members and labels
server/handlers/team_members.go - RLS query pool
server/db/pool.go
Persistent Data
- Board schema and RLS
supabase/schema.sql - Supabase Postgres
Other components
- Board user
Connections 23
- Board user → React entry: opens app
- React entry → Board experience: renders
- Board experience → Supabase client: uses auth and data
- Supabase client → Supabase Auth: authenticates
- Board experience → Supabase Auth: signs in
- Board experience → Board realtime: subscribes
- Board realtime → Supabase Postgres: streams changes
- Board experience → Supabase Postgres: reads and writes
- Board schema and RLS → Supabase Postgres: defines tables and RLS
- Board experience → Authenticated API client: optional API calls
- Authenticated API client → Supabase Auth: gets session JWT
- Authenticated API client → Go API router: sends requests
- Go API router → JWT and CORS middleware: protects routes
- Go API router → Task operations: dispatches tasks
- Go API router → Task comments: dispatches comments
- Go API router → Task activity: dispatches activity
- Go API router → Members and labels: dispatches members and labels
- JWT and CORS middleware → Supabase Auth: verifies Supabase JWT
- Task operations → RLS query pool: queries tasks
- Task comments → RLS query pool: queries comments
- Task activity → RLS query pool: queries activity
- Members and labels → RLS query pool: queries workspace data
- RLS query pool → Supabase Postgres: runs RLS transactions