[Bug] Buildings display deep link changes current view but does not persist after navigation
- Dominant language
- Go
- Stars
- 55
- Forks
- 16
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 87
Description
**Describe the bug**
The Buildings display deep link query parameter changes the current view immediately, but it does not update the stored preference. After navigating away from Buildings and returning, Proto Fleet falls back to the previously saved display mode instead of the deep-linked one.
**To Reproduce:**
1. Start from a state where Buildings is currently saved in grid view.
2. Navigate to `/fleet/buildings?display=list`.
3. Confirm that Buildings renders in list view.
4. Navigate somewhere else in Proto Fleet.
5. Return to Buildings
**Expected behavior:**
Buildings renders in list view. When `/fleet/buildings?display=grid` or `/fleet/buildings?display=list` is used, the selected display mode should become the effective persisted preference so that subsequent navigation continues to use the deep-linked mode.
**Actual behavior:**
The query param only affects the current render. Navigating away and back restores the old stored preference.
**Supporting Material**
- Video attached https://github.com/user-attachments/assets/28dd838d-0388-40b2-9cb0-6c951f38369a
- Reproduced while following the Proto Fleet testing-party checklist scenario: "Deep link with display param"
- The video was referenced in this report but not uploaded from the CLI.
**Environment (please complete the following information):**
- OS: macOS (Darwin)
- Version: Proto Fleet `v0.2.10-rc.5` local RC environment
**Additional context**
This was reproduced in a clean local `fleetnode-ui-test` RC environment on August 13, 2026.
Contributor guide
Research direction
Start by reproducing the issue at /fleet/buildings?display=list, then trace how the Buildings display query parameter is applied and how the stored display preference is updated. Done means both display=list and display=grid remain effective after navigating away from Buildings and returning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100