de1mat opened a new issue, #37693:
URL: https://github.com/apache/superset/issues/37693

   ### Bug description
   
   When a file is created externally (e.g., by Claude Code or another process) 
in a nested folder, clicking the refresh button in the file explorer doesn't 
show the new file. The file only appears after closing and reopening the side 
panel.
   
   **Steps to Reproduce:**
   1. Open a workspace in Superset desktop app
   2. Expand a nested folder (e.g., `src/components/`)
   3. Create a new file in that folder via terminal or external tool
   4. Click the refresh button in the file explorer
   
   **Expected Behavior:**
   New file appears in the tree after clicking refresh.
   
   **Actual Behavior:**
   New file doesn't appear until the side panel is closed and reopened.
   
   **Root Cause:**
   The refresh button only invalidates the root directory cache in the Headless 
Tree library, but nested expanded folders retain their cached children.
   
   ### Screenshots/recordings
   
   _No response_
   
   ### Superset version
   
   Desktop app (Electron)
   
   ### Additional context
   
   The fix is to update `handleRefresh` to invalidate all directories, matching 
the pattern already used by `handleToggleHiddenFiles`.
   
   ### Checklist
   
   - [x] I have searched Superset docs and Slack and didn't find a solution to 
my problem.
   - [x] I have searched the GitHub issue tracker and didn't find a similar bug 
report.
   - [x] I have checked Superset's logs for errors and if I found a relevant 
Python stacktrace, I included it here as text in the "additional context" 
section.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to