feat(admin-dashboard): scaffold Vite + React app for fleet administra…#2
Merged
Conversation
…tion Second frontend audience-focused on fleet administration rather than operator use. Runs on port 5174 and shares the same backend. Capabilities (kept intentionally simple — no WebSocket): - Add vehicle form (POST /vehicles with a name) - Table of vehicles with per-row Set online/offline button hitting PATCH /vehicles/:id/connectivity — surfaces the CANNOT_OFFLINE_ASSIGNED_VEHICLE rejection as a toast so admins see why a toggle failed - Per-row Delete button with confirm dialog - Assignment column names the operator holding the vehicle (fetched once at mount) or falls back to the id suffix - 5-second HTTP polling for freshness Structure mirrors operator-dashboard: strict TS, dark theme reused from the same CSS variables, Toast + useToasts pattern reused verbatim. Kept as a separate Vite app rather than a shared route so the two dashboards can evolve independently — different audiences, different eventual auth scope, different deploy artefacts. Root package.json now fans out to three apps: - install:all installs deps in root + all three apps - dev boots Mongo (docker compose up -d --wait), backend, operator dashboard, and admin dashboard in parallel via concurrently with colored prefixes - new admin:dev / admin:build pass-throughs - frontend:* renamed to operator:* for consistency Commitlint scope allowlist gains 'admin-dashboard'. README expanded to document both dashboards and add a comprehensive architecture, concurrency, testing, and evolution notes section.
maaref-insat
approved these changes
Jul 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…tion
Second frontend audience-focused on fleet administration rather than operator use. Runs on port 5174 and shares the same backend.
Capabilities (kept intentionally simple — no WebSocket):
Structure mirrors operator-dashboard: strict TS, dark theme reused from the same CSS variables, Toast + useToasts pattern reused verbatim. Kept as a separate Vite app rather than a shared route so the two dashboards can evolve independently — different audiences, different eventual auth scope, different deploy artefacts.
Root package.json now fans out to three apps:
Commitlint scope allowlist gains 'admin-dashboard'. README expanded to document both dashboards and add a comprehensive architecture, concurrency, testing, and evolution notes section.
Summary
Changes
Testing
npm testinapps/backendpassesnpx tsc --noEmitpasses in both apps/docsNotes for reviewers