Filebrowser: fix pinned paths for other connections

Open
#206 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
frontend

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.

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
Dominant language
TypeScript
Stars
1
Forks
0
Avg merge
22h 6m
Merged PRs (30d)
12

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stackabletech/cockpit

All issues in stackabletech/cockpit

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.