How msoq/react-gm-2020 works
Project type and purpose
• This is a full-stack mentoring project, combining a React single-page-application (SPA) front end with a lightweight Node/TypeScript mock API server.
• Purpose: display and manage a list of movies via React components, Redux-style state modules, and communicate with a local mock service for CRUD operations.
File structure
• Top-level directories:
– config: Webpack build configurations for dev, prod, and common settings
– server: Express-style TypeScript server with routes, services, and mockData
– shared: TypeScript interfaces shared between front and back ends
– src: React app source (assets, components, hooks, routes, store, styles, utils)
• Patterns & conventions:
– Front-end: component-driven, Redux-pattern modules (store/modules)
– Back-end: MVC-inspired layering (routes → service interfaces → implementations → mock data)
– Build/test tooling: Webpack, Babel, Jest, ESLint, Prettier, nodemon
Detail without over-splitting
• Every meaningful layer: UI, state/store, HTTP client, API routes, service, data.
• Don’t fragment each tiny component—group similar UI widgets or store modules into logical clusters.