How interview-repo/evreka works
Project Type and Purpose
• This is a Single-Page Application (SPA) user management interface (“Evreka Users CRM”) built entirely in React + TypeScript.
• It does not include a real backend; instead it uses MSW (Mock Service Worker) to simulate a REST API for development.
• Key features: list of 5,000+ users (table/card), filtering, pagination modes, modal forms, URL-state management, Leaflet maps, localStorage persistence.
File Structure
• Top-level Vite config & package files → your build/development toolchain.
• public/ → static assets, service worker, manifest.
• src/
• api/ → HTTP client setup (createApiClient).
• components/ → UI primitives & domain widgets (form controls, table, user cards, modal, map components).
• hooks/ → abstraction over data fetching & UI state (useApi/useApiTable via TanStack Query, user-specific hooks).
• integrations/ → TanStack-Query and Router providers & layout wrappers.
• routes/ → page components wired to URL paths (root, user list, user detail).
• mock/ → MSW handlers & fake data generator (Faker.js).
• utils/ → misc helpers (date formatting, validation, localStorage).
• types/ & constants/ → strongly-typed models & enums.
• styles.css → global CSS (Tailwind + Styled Components).
Gather Insights from the README
• Confirms use of React 19, TypeScript strict mode, TanStack Query/Router, Styled Components + Tailwind, Leaflet, Zod validation.
• Clarifies functional domains: user listing, filtering/searching, modal form flows, detail page with interactive map.
• Browser (Client)
• React App
– Routing Layer (TanStack Router)
– State & Data Layer (TanStack Query)
– UI Layer (Components tree)
· Shared components (buttons, inputs, table, cards, map)
· Domain components (UserListPage, UserDetailPage)
– Integration Layer
· API Client (axios/fetch wrapper)
· Mock Service Worker (msw) intercepting API calls
· LocalStorage persistence adapter
· Zod schema validator for form inputs
· Leaflet map controller connecting to external tile server
• Mock API (MSW)
• Endpoint handlers returning fake users from mock/user.service.ts
• Generator seeded with Faker.js
• External Services
• Tile Server (e.g., OpenStreetMap)
• Data Flow
• UI dispatches queries via useApi/useApiTable → TanStack Query cache → API Client → MSW → mock data
• Form submissions validated by Zod → API Client calls → MSW update
• Query results optionally synced to localStorage (URL-based state)
• Build/Dev
• Vite Dev Server serves React App, registers MSW
• Yarn scripts for build, preview, lint
Architectural Patterns & Design Principles
• Component-Driven Architecture: small, reusable UI building blocks.
• Hooks for separation of concerns: data fetching vs. UI logic.
• Provider pattern: central TanStack Query/Router providers wrapping the app.
• Mocking layer decoupled from production API (swap MSW for real endpoints).
• URL-driven state & localStorage persistence for shareable links & reload resilience.
Elements
• Clear component names matching the file tree (e.g., “UserListPage”, “useUsersTable” hook).
• Infrastructure nodes: Vite Dev Server, MSW service worker, Browser LocalStorage.