Problem
The up-front destination check (#216, #217) excludes forced downloads (downloadForced), but the transfer never overwrites an existing file, so a forced import onto an occupied destination still throws DestinationAlreadyExistsException instead of being rejected with a reason (or replacing when that was intended).
Suggested fix
Apply the same classification to forced imports, or define what a forced import should do to an occupied destination. Found while reviewing #217.
Problem
The up-front destination check (#216, #217) excludes forced downloads (
downloadForced), but the transfer never overwrites an existing file, so a forced import onto an occupied destination still throwsDestinationAlreadyExistsExceptioninstead of being rejected with a reason (or replacing when that was intended).Suggested fix
Apply the same classification to forced imports, or define what a forced import should do to an occupied destination. Found while reviewing #217.