How shagundubey1/soar works
Main components
• Frontend Application: The entire application powered by React. This includes:
• Entry point (index.html and src/main.tsx) and the central application component (src/App.tsx).
• Layouts and routing (directories like src/layouts and src/routes) that organize the UI.
• Pages (after all, you have separate pages for accounts, credit cards, dashboard, investments, loans, etc.) which the router maps.
• State Management: Use of Redux Toolkit (illustrated by file entries in src/features and src/stores) to manage global state.
• API and Services: The src/apis contains API calls, while src/services manages external data connections or business logic.
• Configurations and Constants: Including configuration files (src/config) and constants (src/constants) which provide standardized values and notifications.
• Types & Schemas: Type safety enforced through files in src/@types and schema definitions in src/schema.
• Styling & Build Tools: Tailwind CSS (tailwind.config.js, src/styles) and other build configuration (Vite, ESLint/Prettier, etc.)
Relationships and Interactions between Components
• The entry point (main.tsx) loads the App component which further manages the routing and layouts.
• The router (src/routes/routes.tsx) directs users to different pages (under src/pages) based on the URL.
• UI components (in src/components/*) are composed within the pages and layouts (src/layouts) to form the interactive dashboard.
• API services (src/apis and src/services) facilitate data fetching, updating the state or storing transactions.
• The configuration files ensure consistent notifications and styling (e.g., notifyConfig.ts and tailwind.config.js).
Architectural Patterns & Technologies
• Component-Based Architecture: The separation into components (base, shared, UI) reflects a modular design.
• Routing and Layout Separation: Pages and layouts show an MVC-like separation in UI design.
• State Management using Redux Toolkit indicates a unidirectional data flow.
• API Abstraction: API calls centralized in src/apis help maintain separation of concerns.
• Use of Build Tools & Linters (Vite for building, ESLint, and Prettier for code quality) to ensure a maintainable workflow.