Check if StorageInputType needs to be in TranslationSource or in DocumentTranslationInput

The reason why it is in DocumentTranslationInput is that both source and target had to have the same storageInput. I believe the service updated their behavior and this is no longer required, but need to double-check.

If it is no longer needed for a target too, we should move the DocumentTranslationInput.Storagetype property to the TranslationSource type

[ZulaMostafa]

Let’s have a look into the interesting results, I’ve tested all the combinations using both Postman and the actual SDK.

Case 1: Source: Folder Target: Folder Status: Succeeds

Case 2: Source: File Target: Folder Status: Succeeds only if the StorageType is specified as File.

Case 3: Source: File Target: File Status: Succeeds only if the StorageType is specified as File. There is one more comment about this case, it works only if the target is a container with adding filename at the end of the path in the URL. If the target is a blob Postman responds with Ok status but the file never changes. and for the SDK, that was the error I got: Cannot access target document location with the current permissions. Status: 200 (OK) ErrorCode: InvalidTargetDocumentAccessLevel

Case 4: Source: Folder Target: File Status: Fails. When I use a container as the target with adding the file name at the end of the path it creates a new folder. And when i use a blob it’s just the same as the previous case.

I think we need to move StorageType property to TranslationSource. I had to specify the type only if the source was File. Regarding the permissions issue, I’m not sure if I’ve done something wrong but the permissions given to the blob was read and write.

[ZulaMostafa]

It’s true now that source and target can have different storageInput. But I don’t get why should we move the property to TranslationSource, shouldn’t the target have a StorageType too?