How honey-singh716/resolvex works
ResolveX is a multi-tenant issue and service-management SaaS. Users authenticate, select or join an organization, then report and track tickets; organization staff manage issues and membership, while platform administrators verify and oversee organizations. The frontend routes role-specific workspaces through a typed API client to FastAPI endpoints, which enforce authentication and operate on PostgreSQL-backed domain records. Notifications and platform administration are distinct supporting capabilities. The graph emphasizes documented routes and sampled calls; several important backend handlers are indexed but unsampled, so their internal call relationships are left out.
Main entry points: router.py API router · api.ts Typed API client · App.tsx Route application · client_issues.py Client issue routes
Components 24
Frontend experience
- Route application
frontend/src/App.tsx - Authentication state
frontend/src/context/AuthContext.tsx - Organization context
frontend/src/context/OrgContext.tsx - Client ticket dashboard
frontend/src/pages/ClientDashboardPage.tsx - Client ticket detail
frontend/src/pages/ClientTicketDetailsPage.tsx - Issue and org workspaces
frontend/src/pages - Platform admin console
frontend/src/pages/PlatformAdminPage.tsx - Typed API client
frontend/src/services/api.ts
Identity and tenancy
- Authentication routes
backend/app/api/v1/auth.py - Organization routes
backend/app/api/v1/organizations.py
Issue management
- Client issue routes
backend/app/api/v1/client_issues.py - Issue routes
backend/app/api/v1/issues.py
Administration and notifications
- Notification routes
backend/app/api/v1/notifications.py - Platform routes
backend/app/api/v1/platform.py - Notification service
backend/app/services/notifications.py
Backend foundation
- API router
backend/app/api/v1/router.py - Auth dependencies
backend/app/api/deps.py - JWT security
backend/app/core/security.py - Runtime configuration
backend/app/core/config.py - Database session
backend/app/db/session.py - PostgreSQL
- Domain records
backend/app/db/models - API schemas
backend/app/schemas
Other components
- User
Connections 27
- User → Route application: uses
frontend/src/App.tsx - Route application → Authentication state: provides auth
frontend/src/App.tsx - Route application → Client ticket dashboard: routes to
frontend/src/App.tsx - Route application → Issue and org workspaces: routes to
frontend/src/App.tsx - Route application → Platform admin console: routes to
frontend/src/App.tsx - Authentication state → Typed API client: calls auth
frontend/src/context/AuthContext.tsx - Organization context → Typed API client: loads organizations
frontend/src/context/OrgContext.tsx - Client ticket dashboard → Typed API client: requests tickets
frontend/src/pages/ClientDashboardPage.tsx - Client ticket detail → Typed API client: requests ticket
frontend/src/pages/ClientTicketDetailsPage.tsx - Platform admin console → Typed API client: calls admin API
frontend/src/pages/PlatformAdminPage.tsx - Typed API client → API router: HTTP API
- API router → Authentication routes: registers
backend/app/api/v1/router.py - API router → Client issue routes: registers
backend/app/api/v1/router.py - API router → Organization routes: registers
backend/app/api/v1/router.py - API router → Issue routes: registers
backend/app/api/v1/router.py - API router → Notification routes: registers
backend/app/api/v1/router.py - API router → Platform routes: registers
backend/app/api/v1/router.py - Authentication routes → Auth dependencies: uses dependencies
backend/app/api/v1/auth.py - Auth dependencies → JWT security: decodes token
backend/app/api/deps.py - Auth dependencies → Database session: loads user
backend/app/api/deps.py - Database session → Runtime configuration: gets database URL
backend/app/db/session.py - Database session → PostgreSQL: opens sessions
backend/app/db/session.py - Client issue routes → Notification service: notifies comment
backend/app/api/v1/client_issues.py - Client issue routes → Domain records: reads and writes
backend/app/api/v1/client_issues.py - Organization routes → Domain records: reads and writes
backend/app/api/v1/organizations.py - Notification service → Domain records: reads and writes
backend/app/services/notifications.py - Client issue routes → API schemas: validates and responds
backend/app/api/v1/client_issues.py