I'll fix the issue where the main view doesn't display entries after moving files, even though the sidebar shows the correct structure.

I've fixed the issue where the main view doesn't display entries after moving files. The problem was related to how the file system view was being refreshed after move operations. Here are the changes I made:

1. Improved refresh logic: I've updated both handleDrop and handleBreadcrumbDrop functions to use a more robust refresh strategy that:

   • First rebuilds the directory tree to update the sidebar
   • Then explicitly reloads the current directory to update the main view
   • Handles special cases for the root directory
   • Provides fallback navigation if the current directory no longer exists
2. Added a small delay: I added a small delay in the loadDirectory method to ensure filesystem operations complete before returning results. This helps prevent race conditions where the UI might update before the filesystem has fully processed changes.
3. Better error handling: I've improved error handling to ensure that even if there's an issue refreshing the current view, the application will fall back to showing the root directory.

These changes ensure that after moving files or folders:

1. The sidebar correctly shows the updated directory structure
2. The main view properly displays the contents of the current directory
3. The application recovers gracefully if any directories are in an intermediate state

The root cause was likely a timing issue where the UI was being updated before the filesystem operations had fully completed, or the current directory wasn't being properly refreshed after move operations.

I'll add a button to edit files as text when they're less than 2MB and the preview is not available.

I've added the "Edit as Text" button for files that don't have a preview available. Here's what the new feature does:

1. The button only appears for files smaller than 2MB (2 * 1024 * 1024 bytes) to avoid trying to load very large binary files as text

2. When clicked, it attempts to:

   • Load the file using the file handle
   • Convert the file content to text
   • Update the preview type to "text"
   • Display the content in the text editor
3. If the file can't be read as text (which can happen with binary files), it shows an error message explaining that the file may contain binary data
4. The button is styled with the "secondary" variant to distinguish it from the download button

This gives users the flexibility to attempt viewing and editing files that might be text-based but weren't automatically detected as such, like configuration files with unusual extensions or custom file formats.