-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uploader context #23
Uploader context #23
Conversation
- allows for not polluting the session object, or when the session object isn't suitable for passing additional context information
Thank you. I'm glad that people are finding this gem useful. I just realized that Artem's changes in PR #16 were made exclusively in lib.js. When you made the changes to s3mp.js and recompiled the javascript files his changes were reverted. Would you mind patching up the individual js files with his changes and then recompiling again? I'll merge the request after that and push out a new version of the gem. Great work otherwise. |
Will do. Thanks. |
Should be ready to go Max. Thanks again. |
Max,
Thanks for the great gem. I found it impractical to use the session object to pass the additional context information I needed for an uploaded object, so I added a context (text) attribute to the S3Multipart::Upload model itself. This can be set via a data-context attribute on the file input. The attribute can be populated with a Javascript object and parsed as JSON on the server.
I also merged in my other PRs and fixed the package.json to fix grunt at 0.3.17 otherwise npm will install grunt 0.4.x and grunt commands will fail due to your dependency on underscore (I think). I tried to resolve that dependency to move up to lodash, but wasn't able to get that working.
HTH,
-Michael