@uppy/aws-s3: update type and deprecate timeout
option
#4298
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Having a timeout on the client side doesn't make much sense IMO, a more reasonable approach seems to be to use the
Expires
value reported by the backend that tells Uppy when the signature expires (at which point the upload is guaranteed to fail, so it makes sense to cancel the upload).The plan is to remove the option entirely on the next major, at the same time as we combine both
@uppy/aws-s3
and@uppy/aws-s3-multipart
, which doesn't have this option.If you are using this option and would not like it to be removed, please comment on this thread.