Remove extraneous leading forward slash on uploaded files #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.
There's a separate PR here (#8) which does the same thing, but looks to be based off an older version of the repo.
I found when I was using this locally that if I wanted to upload files to the root of the S3 bucket, I wasn't able to -- it would always upload it to a directory that existed in the root, named
/
. So the file foo.txt that I wanted in the root was being uploaded inside of directory /.This seems to be the case when you have an empty
uploadPath
. The filepath (pre-upload path) still has the leading/
from lopping off the base, which is useful for joining theuploadPath
to it and producing a valid directory structure. But when there is nouploadPath
, it still keeps the separator, which throws off the process.