Dropbox.files_delete_batch and similiar methods to support deleting a specific version

We are running an unattended process which uploads files from a raspberry pi. These files can become corrupt.
The corrupt files remain in the file history.

I would like to detect these corrupt file versions and remove them from the version history.

Could the family of Dropbox.file_delete* (e.g. Dropbox.files_delete_batch) support passing the file version ID? DeleteArgs I believe is passed (as opposed to the a dropbox file path), hence it maybe necessary to add another field to DeleteArgs.

It would actually be amazing these methods would also accept FileMetadata instances to save messing around extracting ids, paths etc. But that is another feature: :)

thanks.

Start by inspecting the family of Dropbox.file_delete* methods, including Dropbox.files_delete_batch, and the DeleteArgs type mentioned in the issue. Confirm how file version IDs are represented and whether the API supports deleting specific versions; done means the relevant deletion methods accept version IDs with consistent behavior, while the FileMetadata request remains a separate feature.

Written by the indexing model from the issue text.