WeTransfer-Swift-SDK
WeTransfer-Swift-SDK copied to clipboard
WeTransfer
A Swift SDK for WeTransfer’s public API
Currently `AsynchronousDependencyResultOperation` is used to handle the completion of all running instances of `UploadFileOperation` combined, but only the last result and error are used. This should be fixed by either...
Using `CodingKeys` of `Codable`, properties like `id` should be renamed to `identifier`. All responses should also be renamed to their actual purpose, instead of directly conveying the API implementation details...
Currently the SDK doesn't persist any state so resuming uploads is not possible. It should be able to store information about uploaded chunks so transfer uploads could be resumed at...
Right now `UploadFilesOperation` fails when there aren't any files to upload. This might be undesired as there is no actual failing happening when the transfer already has successfully uploaded files
Right now in `CompleteUploadOperation`, in the success case of the complete upload request, the response is checked and still might fail based on the value of `ok`. The expected responses...
Currently `APIEndpoint` structs contain generic references to the response that is expected to be returned from the request. The request parameters should be defined here as well
UploadFilesOperation should have little to do with creating a new `URLSession` and its delegate method. Ideally `APIClient` should have a method to create a new `APIClient` and accept a closure...
Currently the `Authorizer` class only stores a bearer and adds it to a given request. It should be responsible for the actual authentication and could also handle the case of...
Add the ability to create a transfer with in-memory objects like images. Any object that can be represented as `Data` should be able to be added to a transfer