stackabletech / stackabletech/cockpit
Filebrowser: fix pinned paths for other connections
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- Avg merge
- 22h 6m
- Merged PRs (30d)
- 12
Description
The solution should be as intuitive to the user as possible. As such the following recommendation is made:
- Every storage connection gets a hash from their connection details to quickly identify them uniquely
- Only pinned paths that are associated with a saved connection may be shown in the pinned list
- Upon navigating to a directory from a different connection, the connection must be automatically made to the new storage
- This has to work well with the Tab View feature
- This behavior should include recently accessed paths and locations as well
Contributor guide
No contributing guide indexed for this repository
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 tracing the Filebrowser state for pinned paths, recently accessed paths and locations, then inspect how the Tab View tracks storage connections. Verify navigation between multiple saved connections and ensure paths are associated with the correct connection. Done means only valid saved-connection paths appear, connection changes happen automatically, and the behavior works across tabs and recent locations.
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
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100