Fix bug with config not being highlighted on navbar

[1Blademaster]

No description provided.

[Copilot]

Pull request overview

Updates how the GCS tracks and emits “state” changes, especially around the /config route, so the UI can still update its current page without always emitting a set_state socket event.

Changes:

• Middleware: always updates Redux currentPage on emitSetState, but suppresses the set_state socket emit when the state is exactly "config".
• Layout: always dispatches emitSetState(currentPageLowerCase) (removes the prior "config" special-casing).
• Navbar: adds a console.log(currentPage) debug statement.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
gcs/src/redux/middleware/emitters.js	Prevents socket set_state emission for the "config" state while still updating Redux currentPage.
gcs/src/components/layout.jsx	Always dispatches emitSetState on page changes (including "config").
gcs/src/components/navbar.jsx	Adds a debug log of currentPage.

Comments suppressed due to low confidence (1)

gcs/src/components/layout.jsx:44

• The useEffect uses aircraftTypeString and shouldFetchAllMissionsOnDashboard, but they are not included in the dependency array. This can lead to stale behavior (e.g., missing a loiter radius fetch when aircraftTypeString changes while on the dashboard, or not fetching missions after shouldFetchAllMissionsOnDashboard flips). Add the missing dependencies (and dispatch if you follow exhaustive-deps) or split this effect so each piece has the correct deps.

    dispatch(emitSetState(currentPageLowerCase))

    if (!connectedToDrone) return

    if (currentPageLowerCase == "dashboard") {

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.