Closed sabymike closed 8 years ago
We should note that this is very much a breaking change and should be released under a new major version. I'm all for this change though, :+1:
Maybe add a test with the key
function supplied though.
Updated requested changes including updated test, incremented major version.
Looks awesome!
I want to give some time to let @badunk look thru this though since the change is rather large. But :+1: from me.
Also, maybe we should consider baking in the proposed change about passing in an aws
instance and dropping the dependency on aws-sdk
. On the other hand, maybe that needs some more discussion...
If so I think that should be a separate pull request. How key
is managed and the aws instance are really two separate things. They probably should have been broken out into separate issues.
Yes, it should absolutely be a separate issue, but the version number should probably not be included here though.
Actually, do you mind removing 7fe6354 (the version bump commit)? I'll do that with npm version major
when we are releasing, that will create the correct tags as well. You can do that with git rebase -i master
, just remove the line corresponding to that commit.
Sorry about that, done.
Looks good to me, not sure what I was thinking when I was calling it filename and dir - maybe I wanted to keep to the same multer options names. I prefer the s3 semantics as well.
Thanks!
Let's merge, thanks for the awesome work @sabymike!
Would either of you mind publishing the newest version to npm?
I don't have access so that must be done by @badunk, I would like to get #13 merged first though. Get all the breaking changes now so we don't have to release 3.0.0 in a week again.
Maybe I'll get some time to look at it tonight (Swedish time)
Removes the requirement for
dirname
and changes thefilename
property tokey
. This should resolve issue #9.In addition, extend the payload passed back to multer and ultimately to the request file property with the data that is provided by the s3.upload call.