Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Files Tab: show tree structure option #176

Closed
Willian-Zhang opened this issue Mar 13, 2024 · 6 comments
Closed

Feature request: Files Tab: show tree structure option #176

Willian-Zhang opened this issue Mar 13, 2024 · 6 comments
Labels
fix-committed Fix for the issue is in the main branch

Comments

@Willian-Zhang
Copy link

Explanation of feature

Consider a task with the following simplified structure

- A
  - A.A
  - A.B
- B
  - B.A
  - B.B

currently displayed as the tree structure, with the purposed option, it would be shown as

- A/A.A
- A/A.B
- B/B.A
- B/B.B

with this option, one can easily manage multiple files with search or order feature

@qu1ck
Copy link
Member

qu1ck commented Mar 13, 2024

So you want an option to NOT show the tree structure and just display a flat list of files?

What kind of operation you want to perform that would be easier with such presentation?

@Willian-Zhang
Copy link
Author

Willian-Zhang commented Mar 13, 2024

So you want an option to NOT show the tree structure and just display a flat list of files?

exactly!

What kind of operation you want to perform that would be easier with such presentation?

all the right click submenu items, priories, wanted/unwanted

@qu1ck
Copy link
Member

qu1ck commented Mar 13, 2024

I still don't see how does flat list make any of those easier.

@Willian-Zhang
Copy link
Author

Willian-Zhang commented Mar 13, 2024

well say you want *.B (to be bulk edited) in the example case, you would have to manually select them in that case.

but with a flat representation, you could search .B as a keyword and have all the result selected with shift-clicks.

@qu1ck
Copy link
Member

qu1ck commented Mar 14, 2024

I see, that makes sense. It will be added.

@qu1ck qu1ck added the fix-committed Fix for the issue is in the main branch label Mar 19, 2024
@qu1ck
Copy link
Member

qu1ck commented Apr 15, 2024

Implemented in v1.3.0

@qu1ck qu1ck closed this as completed Apr 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fix-committed Fix for the issue is in the main branch
Projects
None yet
Development

No branches or pull requests

2 participants