I re-downloaded the openapi specification today and did a diff with the one I downloaded in September. I noticed a change that can simplify the rclone backend.
"MoveFolderDto": {
"type": "object",
"properties": {
"destinationFolder": {
"type": "string",
"example": "366be646-6d67-436e-8cb6-4b275dfe1729",
"description": "New Destination Folder UUID"
},
"name": {
"type": "string",
"description": "New folder name (optional). Specify it to rename the folder when moving",
"example": "newName"
}
},
"required": [
"destinationFolder"
]
},The "name" property wasn't there on the old one. It seems Internxt now supports renaming a file (MoveFileDto) or folder (MoveFolderDto) while moving it, in a single call. Supporting this in go-internxt-drive could significantly simplify the Move func in the rclone backend as we could skip the temporary renaming. This in turn cuts down on API calls and should also result in some speedup seeing as we're currently sleeping between the calls as well.
I re-downloaded the openapi specification today and did a diff with the one I downloaded in September. I noticed a change that can simplify the rclone backend.
The "name" property wasn't there on the old one. It seems Internxt now supports renaming a file (MoveFileDto) or folder (MoveFolderDto) while moving it, in a single call. Supporting this in go-internxt-drive could significantly simplify the Move func in the rclone backend as we could skip the temporary renaming. This in turn cuts down on API calls and should also result in some speedup seeing as we're currently sleeping between the calls as well.