How nikunjgupta9os/uat works
Project type and purpose
• This is a single-page web application (SPA) built with React, TypeScript and Vite.
• The focus is a financial dashboard suite: CFO dashboard, OPS dashboard, MTM calculators, FX booking and exposure modules, user‐access management, report generation, and more.
• There is no custom backend code in the repo (the server/ folder only contains a README), so the app consumes external or internal REST/GraphQL APIs for data and authentication.
File structure
• Top‐level files:
• index.html, main.tsx, App.tsx – entry point and root component.
• ProtectedRoute.tsx – handles client‐side auth routing.
• Vite, ESLint, PostCSS, Tailwind and TypeScript config files – build & lint infrastructure.
• src/client/ – all feature modules, organized by domain:
• CFODashboard, OPSDashboard, Reports, Settlement, MTMCalculator, DashboardBuilder, MTMRateInput, Notification, linkingScreen, uam (Users/Permissions/Roles).
• fx/ – deep hierarchy of submodules for net positions, exposure upload, cancellations, forwards, hedging proposals and wizards.
• src/client/common/ – shared UI (Navbar, Sidebar, Footer, table utilities, drag-and-drop helpers, form validation, theme toggle).
• src/client/contexts/ThemeContext.tsx – app-wide theme management using React Context.
• src/components/ – small reusable inputs and select components.
• No state management library (Redux/MobX) – local state via hooks and a custom store in DashboardBuilder (useDashboardStore.tsx).
README for additional insights
• It’s a Vite-React-TS starter template with HMR, ESLint, Babel/SWC plugins.
• No mention of backend frameworks, so all API calls are external.
Final reminders
• Be exhaustive: capture all essential feature clusters and external dependencies.
• Keep it hierarchical: top-level separation → detailed internals for one or two representative modules.