Drag and Drop Copy Sync or Replace UI#1975
Conversation
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
This implementation of fileContentAtom seems incorrect but it prevents the code editor from rerendering when the contents change. Because of this, it makes sense to use it in the meantime.
This updates the test behavior to match its description
Prior to this change, copying a directory to a directory that did not already exist resulted in the new directory containing the original one. This updates that so the new directory is the same as the original one but with a different name.
We previously only handle the case of copying the current directory to an existing directory. This adds another case for when the target directory does not exist.
This adds the following changes: - adds a button to perform a merge if a drag and drop copy fails - only shows the merge option for directories - renames the overwrite option to "delete then copy" for clarity
WalkthroughThe changes span modifications in file copy handling, directory navigation, and type enhancements. In the directory preview component, a boolean property is added to indicate directory items, and function signatures are updated to accept this property for copy and retry operations. The drag-and-drop functionality is adjusted to carry this new information, and error handling logic now checks for additional specific error messages. In the preview component, methods for obtaining parent directory information have been updated by replacing the previous API call with a new one that formats remote URIs. Logging in navigation methods has also been updated to clarify when a parent directory does not exist. Lastly, the custom type declaration for dragged files is enhanced by including a boolean property to indicate whether the dragged item is a directory. 📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (3)
⏰ Context from checks skipped due to timeout of 90000ms (3)
🔇 Additional comments (8)
✨ Finishing Touches
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Co-authored-by: Evan Simkowitz <esimkowitz@users.noreply.github.com> Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> Co-authored-by: sawka <mike@commandline.dev>
No description provided.