How harrinisri12/budget_management works
This is a college CSE budget-management portal: faculty authenticate, prepare and submit activity proposals, while administrators manage faculty, academic-year allocations, proposal decisions, budgets, transactions and reports. The React application uses shared auth and budget state, with an Express API and Supabase persistence/authentication. The graph captures documented route mounting and sampled data access; several page capabilities are identifiable from the tree and routing, but their internal calls were not sampled, so those links are intentionally omitted.
Main entry points: App.jsx Route guards · server.js Express API router · BudgetContext.jsx Budget state and data access · auth.js Token authentication
Components 24
Web portal
- Route guards
src/App.jsx - Authentication screens
src/pages/LoginPage.jsx - Proposal submission
src/pages/NewProposalPage.jsx - Faculty dashboard and proposals
src/pages/FacultyDashboardPage.jsx - Proposal review
src/pages/AdminProposalsPage.jsx - Academic-year management
src/pages/AcademicYearsPage.jsx - Budget, reports and activities
src/pages/BudgetOverviewPage.jsx - Faculty administration
src/components/faculty/FacultyList.jsx - Auth state
src/context/AuthContext.jsx - Budget state and data access
src/context/BudgetContext.jsx - API client
src/lib/api.js
API and access
- Express API router
server/server.js - Authentication routes
server/routes/auth.js - Faculty routes
server/routes/faculty.js - Proposal routes
server/routes/proposals.js - Budget routes
server/routes/budgets.js - Academic-year routes
server/routes/academicYears.js - Transaction routes
server/routes/transactions.js - Token authentication
server/middleware/auth.js - Role authorization
server/middleware/roles.js
Supabase services
- Server Supabase client
server/supabaseClient.js - Supabase platform
src/lib/supabase.js
Other components
- Faculty user
- Administrator
Connections 41
- Faculty user → Route guards: uses portal
src/App.jsx - Administrator → Route guards: uses portal
src/App.jsx - Route guards → Authentication screens: routes to
src/App.jsx - Route guards → Proposal submission: routes to
src/App.jsx - Route guards → Faculty dashboard and proposals: routes to
src/App.jsx - Route guards → Proposal review: routes to
src/App.jsx - Route guards → Academic-year management: routes to
src/App.jsx - Route guards → Budget, reports and activities: routes to
src/App.jsx - Authentication screens → Auth state: authenticates via
src/pages/LoginPage.jsx - Proposal submission → Budget state and data access: reads and submits
src/pages/NewProposalPage.jsx - Faculty dashboard and proposals → Budget state and data access: reads data
src/pages/FacultyDashboardPage.jsx - Proposal review → Budget state and data access: reads data
src/pages/AdminProposalsPage.jsx - Academic-year management → Budget state and data access: updates years
src/pages/AcademicYearsPage.jsx - Faculty administration → Budget state and data access: manages faculty
src/components/faculty/FacultyList.jsx - Auth state → Supabase platform: authenticates and reads profiles
src/context/AuthContext.jsx - Budget state and data access → API client: requests API data
src/context/BudgetContext.jsx - Budget state and data access → Supabase platform: fallback reads
src/context/BudgetContext.jsx - API client → Express API router: calls API
- Express API router → Authentication routes: mounts
server/server.js - Express API router → Faculty routes: mounts
server/server.js - Express API router → Proposal routes: mounts
server/server.js - Express API router → Budget routes: mounts
server/server.js - Express API router → Academic-year routes: mounts
server/server.js - Express API router → Transaction routes: mounts
server/server.js - Authentication routes → Token authentication: uses
server/routes/auth.js - Faculty routes → Token authentication: uses
server/routes/faculty.js - Proposal routes → Token authentication: uses
server/routes/proposals.js - Budget routes → Token authentication: uses
server/routes/budgets.js - Academic-year routes → Token authentication: uses
server/routes/academicYears.js - Transaction routes → Token authentication: uses
server/routes/transactions.js - Faculty routes → Role authorization: checks roles
server/routes/faculty.js - Proposal routes → Role authorization: checks roles
server/routes/proposals.js - Academic-year routes → Role authorization: checks roles
server/routes/academicYears.js - Transaction routes → Role authorization: checks roles
server/routes/transactions.js - Token authentication → Server Supabase client: validates token and profile
server/middleware/auth.js - Authentication routes → Server Supabase client: uses
server/routes/auth.js - Faculty routes → Server Supabase client: uses
server/routes/faculty.js - Proposal routes → Server Supabase client: uses
server/routes/proposals.js - Budget routes → Server Supabase client: uses
server/routes/budgets.js - Academic-year routes → Server Supabase client: uses
server/routes/academicYears.js - Transaction routes → Server Supabase client: uses
server/routes/transactions.js