Description

FileManager calls Create and Destroy instead of Update on move.

That is not what happens in the file system. Move is Update operation where the location of the item is updated. No files are copied or deleted.

Copying files and directories unnecessarily wastes the resources on the server and the cloud where computing and storage operations are charged.

If Destroy fails which might happen because Create and Destroy are executed separately then files are copied and not moved.

Expected behavior

Move calls Update.

The FileManager triggers two Read requests when double clicking a folder in the ListView/GridView. The behavior can be observed in the Basic Usage Demo.

When navigationg to a folder in the TreeView using a single click, the component triggers a single Read request.

Could you consider optimizing the request handling when navigating to nested folders, particularly in ListView/GridView, to reduce redundant Read calls and improve performance?