microsoft / microsoft/fabric-cli
[FEATURE] Easy way to get folder path for items
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 173
- Forks
- 63
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 4
Description
Use Case / Problem
The newer "fab config set folder_listing_enabled true" mode is great, but I also really liked the ability to have that OFF/false in order to get ALL items in a workspace in one call without recursively navigating the folder structure. However, when I have folder_list_enabled false, I don't see a way to get the item folder path when running fab ls (or fab ls -l). Can we add item folder path to the ls-l output?
Proposed Solution
Please add the item folder path to the
fab ls -l
output. Or add another flag to ls? Or?
Alternatives Considered
Workaround is to set folder_listing_enabled to true, then write looking code to navigate the folders recursively. It's a bit of a PITA.
Impact Assessment
- This would help me personally
- This would help my team/organization
- This would help the broader fabric-cli community
- This aligns with Microsoft Fabric roadmap items
Implementation Attestation
- I understand this feature should maintain backward compatibility with existing commands
- I confirm this feature request does not introduce performance regressions for existing workflows
- I acknowledge that new features must follow fabric-cli's established patterns and conventions
Implementation Notes
No response
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 tracing the fab ls and fab ls -l implementations and how folder_listing_enabled affects item listing. Determine whether the existing listing data includes folder paths, then define the output or flag behavior so fab ls -l exposes each item’s path when folder listing is disabled without changing existing output unexpectedly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100