How jimhuertas123/task-manager-challenge-app works
Project type and purpose
• This is a single-page application (SPA) “Task Manager App” built with React, TypeScript, Vite, and Apollo Client for GraphQL.
• Purpose: Provide a dashboard UI for users to create, view, update, and delete tasks organized by status (Backlog, Todo, In Progress, Done, Cancelled).
File structure
• Top-level build & config:
• vite.config.ts, package.json, tsconfig.json (build tooling)
• codegen.ts and src/__generated__ (GraphQL Code Generator)
• .github/workflows/*.yml (CI/CD pipelines)
• .husky and lint configs (pre-commit hooks, linting)
• src/
• pages/ – Route-level pages (DashboardPage, MyTasksPage, ErrorPage, NotFoundPage)
• components/
– layout/ (MainLayout, NavBar, PhoneNavBar, NavLinkCard)
– features/ (FormNewTask, ModalTask, SearchTasks, TaskCards)
– ui/ (generic UI primitives: GridCards, ListCards, Popover, etc.)
• graphql/ (fragments, queries, mutations)
• lib/ (apolloClient setup, constants, router)
• contexts/ (UsersContext, EditTaskModalContext, custom hooks)
• hooks/ (useMediaQuery)
• main.tsx & index.html (app entry point)
README for additional insights
• Feature-driven development: structure groups related features under src/components/features.
• CI/CD via GitHub Actions and Vercel for preview/production.
• Tech stack: React, TypeScript, Vite, React Router DOM, Apollo Client, GraphQL Code Generator, linting/formatting/husky.
Final recommendations
• Be detailed: break the SPA into individual modules (pages, features, UI, contexts, lib).
• Data flow: from user event, through React components, through Apollo to the API and back.
• Lifecycle: local dev (Vite) → codegen → build → deploy → runtime.