Allow Transloadit-hosted Companion with other uploaders #5558
+70
−12
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.
We want to allow people to only use Transloadit for Companion, even if they use another uploader. This makes using Transloadit less all-or-nothing.
Unfortunately there is no pretty way of doing this. Instead of separating Companion logic from uploaders, every uploader implements remote uploads themselves. It works like this:
@uppy/google-drive
)@uppy/companion-client
) and@uppy/provider-views
@uppy/provider-views
we calluppy.registerRequestClient()
to put the request client on core so it can be shared.this allows us to do rate limiting and synchronous operations like refreshing provider tokens
example: refreshing tokens: if each file has their own requestclient,
we don't have any way to synchronize all requests in order to block all requests, refresh the token, and unblock all requests and allow them to run with a the new access token.
@uppy/aws-s3
) filters the remote files and gets the instructions to tell Companion what uploader to use:uppy/packages/@uppy/aws-s3/src/index.ts
Lines 925 to 972 in d6156bb
With this PR you can do this:
This is the least ugly way I could come up with.