How scvapp/scvappfrontend works
Project type and purpose
• This is a single-page web application (SPA) built with Create React App.
• It uses React Router for client-side routing and Redux Toolkit for state management.
• It provides user-facing pages (login, meals, schedule, settings, about), plus an admin panel (door-passes, schedule editing, logs).
• It calls out to external REST APIs (e.g. adminDoorPassAPI, settingsAPI, meals Web API, user data API) and integrates with Microsoft authentication for login.
File structure
• “src/index.js” bootstraps the React app and Redux store at “src/app/store/store.js.”
• “src/Route” defines route wrappers (LoginRoute, MealsRoute, AdminRoute, etc.) that enforce authentication or feature flags.
• “src/app/store” holds the Redux slices under “src/features” (alert, apps, doorPasses, mealUser, sideMenu, theme, user, etc.).
• “src/pages” holds page-level containers grouped by feature: homePage, loginPage, mealsPage, settingsPage, aboutPage, adminPanel (with nested components and utilities like adminDoorPassAPI.js), etc.
• Utilities and hooks (useDoorPasses, useAlert, useSideMenu, userHook) encapsulate side-effect logic and API calls.
README
• No custom architecture docs—just default CRA scripts.
• We infer front-end only; back end is external.
a. Main components (group into four layers):
1) Client-side Browser / PWA Shell
• index.html + service worker + manifest (public/)
2) Presentation Layer (React)
• React Router (src/Route)
• Page containers (src/pages)
• Presentational components (src/components & nested admin/components, meals/components, settings/components)
3) State & Logic Layer
• Redux store (src/app/store)
• Feature slices (src/features)
• Custom hooks (useDoorPasses, userHook, themeHook)
4) Data / API Layer
• REST calls: adminDoorPassAPI, settingsAPI, getMealUser, userGetData
• External Auth (Microsoft OAuth)
• Backend services: Authentication Service, eAsistent API, Meals API, Logging Service
b. Relationships & interactions
• Router renders the appropriate Page container → inside it, Presentation components dispatch actions to Redux.
• Redux middleware / thunks call REST APIs → update feature slices → store changes propagate back to components.
• Components subscribe to store via useSelector or hooks.
• Admin pages call adminDoorPassAPI for CRUD door-pass operations.
• Theme selection persists (e.g. localStorage) via themeSlice.
• SideMenu logic (useSideMenu) toggles navigation panels based on user permissions.
c. Architectural patterns & principles
• Layered separation (Presentation, State, Data)
• Container vs. Presentational components
• Redux Toolkit: slice pattern, centralized store
• React Router guards (Route wrappers) for auth and feature gating
d. Key technologies & libraries
• React, React DOM, React Router v6
• Redux Toolkit, React-Redux hooks
• CSS modules / plain CSS for styling
• CRA build toolchain (Webpack, Babel)
• PWA features via manifest.json, service worker (default CRA)