Open arnav-kr opened 1 week ago
For a temporary fix, I edited library source to ignore local paths when prefix is supplied, it works, I'd still like to know the intended way of doing so
Hi @arnav-kr thanks for the question. The original intent was to mirror the same directory structure from local to storage. Obviously as you bumped into this can be improved. Currently destination
isn't directly settable in uploadMany
We can probably add some additional options to offer a greater degree of flexibility such as not mirroring the entire path structure and only using prefix. I can take a look at making these improvements in the near future.
Probably in options, something like a destinationBuilder
would make it more flexible, than specifing a string, as this way we can get the filename and process accodingly
...
destinationBuilder: (path, additionalParams) => {
let dest;
// perform operation on path
return dest;
}
...
I have a local directory and I want to upload its contents to cloud storage, but when using
transferManager.uploadManyFiles
with either the directory name, or array of files, the destination of the file in cloud storage is taken from the local file path.local directory structure:
here's my code
when uploaded with following code, it becomes
the prefix property works, but I want to upload files directly to
avatars/
there seem to be apassthroughOptions
that can take a destination, but when usinguploadManyFiles
we don't know the exact file names, so can't make the full pathShouldn't it be that while using
prefix
, property, the local file path shouldn't be considered?