feat(ls): add visual divider between folders and items in workspace listing

[Copilot]

✨ Description of new changes

When listing workspace contents with folder_listing_enabled=true and output_format=text, folders and items were displayed in a flat mixed list with no visual separation, reducing readability.

This change adds a visual divider (------------------------------) between folders and items to improve readability when listing workspace contents.

• Summary: Adds a visual divider between folders and items in fab ls workspace listing output. The divider only appears when folder_listing_enabled=true, output_format=text, and --long flag is NOT provided. The divider is inserted as a data entry in the sorted results, requiring no changes to rendering logic or core output classes.

• Context: The original issue requested better visual distinction between folders and items in workspace listings, similar to the behavior when using -a flag for virtual workspace items. This improves readability and helps users quickly identify folders vs. items in large workspaces.

• Dependencies: None - uses existing infrastructure and utilities.

Implementation Details

Divider as a data entry:

• Private constant _DIVIDER = "------------------------------" defined in fab_fs_ls_item.py
• Private method _sort_ws_elements_with_seperation_by_type_order() groups elements by type (Folder, Item), sorts each group using existing sort_ws_elements(), and inserts divider between non-empty groups
• Type order (Folder, Item) is hardcoded within the private method as it is specific to ls on items
• Divider only applied when all conditions are met:
  • folder_listing_enabled=true (config setting)
  • output_format="text" (not JSON)
  • --long flag NOT provided

Code organization:

• All divider-related logic is encapsulated as private methods in fab_fs_ls_item.py
• Keeps the functionality specific to ls on items, improving separation of concerns
• Reuses existing sort_ws_elements() from fab_cmd_fs_utils.py for consistency
• No changes to fab_ui.py, fab_output.py, or fab_cmd_ls_utils.py

Behavior Examples

When folder_listing_enabled=true, output_format=text, and WITHOUT --long flag:

Folder1.Folder
Folder2.Folder
------------------------------
Notebook1.Notebook
Lakehouse1.Lakehouse

When using --long flag or JSON output:

• No divider shown (original behavior preserved)

Testing

• New test test_ls_workspace_with_folders_and_items_divider() added to verify divider functionality (marked as skip, requires VCR cassette recording in live environment)
• All existing tests pass
• Manual verification confirms correct behavior in all scenarios
• Backward compatibility maintained

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[FEATURE] better display ls workspace items with folders (add divider)</issue_title>
<issue_description>### Use Case / Problem

when listing items within a workspace, e.g., 'fab ls ws1.workspace', and the config folder_listing_enabled equals true and the config output_format is text, the ouptut is flat with mixed folders and items.

Proposed Solution

ideally it will be better do have some distinction in the results, like we do when pass -a that divide the output of virtual workspace items. only relevant in text output format.

Alternatives Considered

No response

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</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes [FEATURE] better display ls workspace items with folders (add divider) #18

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.