oxidecomputer / oxidecomputer/console
Returning from user settings page can be confusing
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 228
- Forks
- 22
- Avg merge
- 19h 42m
- Merged PRs (30d)
- 32
Description
User settings are globally accessible (as they should be) – but because this is a dedicated route, it can be disorientating to figure out how to get back to where you were. We could potentially use a modal here, triggered by a param – but until we do some more exploration there's a signfiicant improvement that could be made.
If we pass a return to param we can prompt the user to go back there (this would need to be preserved after navigating between the pages in user settings). If no return param is present we can return to the projects index.
Potentially borrowing this pattern from the serial console.
We should also be adding the settings page as a breadcrumb in the top bar to help orient the user.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining the user settings route and the navigation pattern used by the serial console. Trace how navigation between user settings pages could preserve a return-to parameter, and inspect the top bar breadcrumb area. Done means users can return to the originating location, fall back to the projects index when no parameter exists, and see user settings in the breadcrumb.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100