[BUG] TEST: Potential Bug — Folder (upstream #101)

[ayeshurun]

📋 Copied from microsoft/fabric-cli#101 for AI triage testing.
Expected triage outcome: Potential Bug

---

Bug Description

If I have
W1.Workspace.F1.Folder.<10 ITEMS>

fabric-cli version

fab version 0.1.10 (2025)

Python version

Python 3.13.11

Operating System

Windows

CLI Mode

Command line mode

Authentication Method

Interactive browser login

Steps to Reproduce

CASE 1

:>fab ls /W1.Workspace

LKH01.SQLEndpoint
LKH01.Lakehouse
CPipeline.DataPipeline
...

CASE 2

:>fab ls /W1.Workspace/F1.Folder
ERROR: ls: [InvalidPath] Invalid path: /W1.Workspace/F1.Folder

Expected Behavior

Expected 1

F1.Folder.LKH01.SQLEndpoint
F1.Folder.LKH01.Lakehouse
F1.Folder.CPipeline.DataPipeline

Or ONLY items under root W1, but is doing recursive drill-down

Expected 2
Return ONLY items under this path

[github-actions]

🅰️ Approach A (Action) — prompt-only, no codebase access

AI Assessment: Potential Bug

The report indicates that fab ls /W1.Workspace/F1.Folder returns [InvalidPath], which is not consistent with the documented hierarchy semantics. The CLI is expected to support deep nested folders and dot-suffix entity naming (source: hierarchy docs). The path syntax used appears correct per documentation, and nested folders (up to ~10 levels) are officially supported, so an "InvalidPath" error in this context suggests possible mishandling of nested folder parsing or entity resolution within the CLI.

The output discrepancy (recursive listing vs. expected flat listing) on /W1.Workspace may indicate a bug in scoping or path resolution logic affecting both listing and path validation. Since folders and entities are dot-suffixed and the path provided matches the expected pattern, the "InvalidPath" error should not occur unless the folder truly does not exist, which is not indicated by the report.

This report does not touch authentication or sensitive areas, but correct path resolution is foundational for basic usage. The report is clear, and the commands are valid according to reference.

Next Steps
🔔 Escalated to team — This issue requires team review and has been flagged for attention.

---

💡 If this issue requires the team's attention and was not escalated, you can tag @microsoft/fabric-cli-dev to notify the team.

---

🏷️ Label Decisions (testing mode — not applied)

Decision	Value
AI assessment	ai:bug-triage:potential bug
Would add help wanted	❌
Would add ai:needs team attention	✅
Would request author feedback	❌
Would remove needs triage	❌
Would auto-close	❌
Would notify team	✅

[github-actions]

🅱️ Approach B (Code Agent) — code-aware triage agent that reads the actual source code

AI Assessment: Potential Bug

The report describes a scenario in which listing the contents of a workspace with fab ls /W1.Workspace returns items from a folder beneath the workspace (e.g., F1.Folder.LKH01.SQLEndpoint instead of items at the workspace root). Additionally, attempts to list a nested folder directly (fab ls /W1.Workspace/F1.Folder) result in an "InvalidPath" error, even though the folder exists and the path syntax matches documented structure.

This behavior deviates from the CLI's documented hierarchy and path resolution logic (docs), which supports nested folders and expects /Workspace.Folder and deeper paths to be valid for listing with ls. According to the parser code, folders should be handled as valid path elements and ls should list their contents instead of failing with an InvalidPath. The error suggests potential issues with folder path parsing, validation, or entity retrieval in the implementation, especially given the correct output for workspace root but invalid handling for direct folder listing.

There is also a concern that the root ls command is recursively drilling into folders rather than listing only top-level items, which is inconsistent with POSIX utility conventions and the CLI's documented default behavior.

Next Steps

🔔 Escalated to team — This issue requires team review and has been flagged for attention.

---

💡 If this issue requires the team's attention and was not escalated, you can tag @microsoft/fabric-cli-dev to notify the team.

---

🏷️ Label Decisions (testing mode — not applied)

Decision	Value
AI assessment	Potential Bug
Would add help wanted	❌
Would add ai:needs team attention	✅
Would request author feedback	❌
Would remove needs triage	❌
Would auto-close	❌
Would notify team	✅

[github-actions]

AI Assessment: Potential Bug

The described behavior indicates that fab ls is inconsistently handling workspace and folder paths. Listing the workspace root returns items as if they are recursively enumerated through subfolders, but listing a specific folder results in a path error. Per documented hierarchy and command reference (Hierarchy docs, ls command doc), the CLI should support listing valid folders without invalid path errors and not automatically recurse unless specifically commanded.

The invalid path error in CASE 2 suggests either incorrect parsing of folder paths or broken entity resolution logic, especially since the workspace path is accepted but folder paths are not. The recursive listing in CASE 1 deviates from standard ls utility conventions; items should not be flattened into compound names unless requested, and folders should be navigable directly.

Severity is elevated due to potential regression in folder path resolution and entity hierarchy traversal, affecting access to nested resources and breaking expected filesystem semantics.

Next Steps
🔔 Escalated to team — This issue requires team review and has been flagged for attention.

---

💡 If this issue requires the team's attention and was not escalated, you can tag @microsoft/fabric-cli-dev to notify the team.

[github-actions]

🔔 @microsoft/fabric-cli-dev — This issue has been flagged by AI triage as requiring team attention. Please review the assessment above.