In FileManager read request is triggered twice when navigating to a parent folder that has a nested folder. The issue does not occur if the folder contains only files without a nested folder.
Two identical requests are sent when the parent folder is selected.
There should be a single request when navigating to a parent folder, even if it has a nested child folder.
I am running into inconsistencies when using the toolbar Search input of a File Manager object after navigating to new folders.
Simple dojo for reference - https://dojo.telerik.com/aPOtiXex/2
Steps to reproduce
I am not sure what the best answer for this scenario would be. Maybe navigating to a new folder should clear the search filter criteria in the toolbar and clear any applied filter criteria to the previous folder? Or maybe the toolbar search input should be reset to accurately reflect the current applied filter for the folder on navigate? Something good for your dev team to discuss, but it is clear that the current implementation will create some confusion for users.
In the FileManager, if you configure the Grid as editable through the views.grid option, clicking on the editable Grid cells results in duplicated row data.
Workaround: - use the setOptions method to enable editing in the Grid - https://dojo.telerik.com/uMAxULUR/4
The row data is duplicated
The row data shouldn't be duplicated
We allow the user to rename files and folders, but if they rename to the same name as another file/folder, what we would like to do is prompt the user with a confirmation dialog, explaining that if they click "Ok", the existing file will be overwritten with the newly-renamed file. For folders, it would merge the contents, but again, duplicates would be overwritten. If they click "Cancel", then the dialog should close, and nothing else should happen.
Right now, the closest thing I could find was the "requestStart" event handler. This fires after the user renames, and before the request is sent to the server. The problem is, even in the documentation, it says, "This event can be prevented only for read requests."
We would like to be able to prevent "update" requests as well, for this scenario. Can this be added as a feature?