[GH-ISSUE #5474] [feature]: Sidebar auto-expand and scroll to active file in app #2099

New issue

Open

opened 2026-03-16 23:11:46 +03:00 by kerem · 0 comments

kerem commented

2026-03-16 23:11:46 +03:00

Owner

Originally created by @Atomized-titan on GitHub (Oct 9, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5474

Is there an existing issue for this?

I have searched the existing issues

Summary

When opening an endpoint or file in the Hoppscotch app, the sidebar doesn't automatically expand parent folders or scroll to show the currently active file. All folders remain collapsed even when actively working on a file within them, requiring manual navigation each time to locate the active file in the sidebar tree.

Why should this be worked on?

This significantly impacts user experience because:

Users lose context of where they are in the file structure
Manual navigation is required every time to locate the active file
This is especially problematic with deeply nested folder structures
It breaks the typical IDE-like behavior users expect from similar tools (VS Code, IntelliJ, etc.)
Increases friction and slows down workflow when switching between files

Current behavior

Open any endpoint/file from a nested folder in the desktop app
The file opens in the editor pane
The sidebar shows all folders collapsed after you restart the app or close the folder and come back to that file.
User must manually expand folders to find the currently active file
No ample visual indication of which file is currently open in the sidebar (just a green dot if spotted)

Expected behavior

When an endpoint/file is opened, the sidebar should automatically:

Expand all parent folders containing the active file
Scroll to make the active file visible in the viewport
Highlight or indicate the currently active file
Maintain this context during navigation between files

Additional context

I'd like to contribute a fix for this. I'm looking for guidance on:

Which components/files handle sidebar state management in the desktop app
Any existing patterns or utilities for tree navigation in the codebase
Whether this should be a toggle-able setting or default behavior
Any architectural considerations I should be aware of

This would be a great improvement for the desktop app's usability and bring it in line with standard IDE behavior that users expect.

Originally created by @Atomized-titan on GitHub (Oct 9, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5474 ### Is there an existing issue for this? - [x] I have searched the existing issues ### Summary When opening an endpoint or file in the Hoppscotch app, the sidebar doesn't automatically expand parent folders or scroll to show the currently active file. All folders remain collapsed even when actively working on a file within them, requiring manual navigation each time to locate the active file in the sidebar tree. ### Why should this be worked on? This significantly impacts user experience because: - Users lose context of where they are in the file structure - Manual navigation is required every time to locate the active file - This is especially problematic with deeply nested folder structures - It breaks the typical IDE-like behavior users expect from similar tools (VS Code, IntelliJ, etc.) - Increases friction and slows down workflow when switching between files ## Current behavior 1. Open any endpoint/file from a nested folder in the desktop app 2. The file opens in the editor pane 3. The sidebar shows all folders collapsed after you restart the app or close the folder and come back to that file. 4. User must manually expand folders to find the currently active file 5. No ample visual indication of which file is currently open in the sidebar (just a green dot if spotted) ## Expected behavior When an endpoint/file is opened, the sidebar should automatically: 1. Expand all parent folders containing the active file 2. Scroll to make the active file visible in the viewport 3. Highlight or indicate the currently active file 4. Maintain this context during navigation between files ## Additional context I'd like to contribute a fix for this. I'm looking for guidance on: - Which components/files handle sidebar state management in the desktop app - Any existing patterns or utilities for tree navigation in the codebase - Whether this should be a toggle-able setting or default behavior - Any architectural considerations I should be aware of - This would be a great improvement for the desktop app's usability and bring it in line with standard IDE behavior that users expect.