Problem

I'd like to send many files in the same time but with different files metaData.
The combination of uppy.setMeta uppy.addFile doesn't wok because the upload is asynchronous, and when files finish to upload they will heritate the last uppy.setMeta configuration.

Moreover the uppy.setFileMeta method is quite impossible to use, because on uppy.addFile we can't declared an id

The documentation as of now lacks a sample example of uploading files to S3 bucket. All it says in the documentation is an upload url - "upload/post" which fails to demonstrate exactly how to handle security related stuffs like header, S3 endpoint, access key, etc.

At minimum, the documentation should lay out what things to consider while using this library to upload files to AWS S3 bucket.

Currently, there are 66 total issues detected by CodeClimate: https://codeclimate.com/github/elninotech/uppload/issues?category=complexity&engine_name%5B%5D=structure&engine_name%5B%5D=duplication

Some of these are false positives (like i18n files counting as duplicates), and some of these are easy to fix (like high function cognitive load due to functions longer than 25 lines).

This issue w

When i start lolisafe .js i got warnings
`Knex:warning - Use async .hasTable to check if table exists and then use plain .createTable. Since .createTableIfNotExists actually just generates plain "CREATE TABLE IF NOT EXIST..." query it will not work correctly if there are any alter table queries generated for columns afterwards. To not break old migrations this function is left untouched for now,

@burzum I started some document changes (#197), but I'm still not comfortable using the plugin. Especially the event system. For example, following the upload example I get a unable to export object: StorageManager::get() first arg must be a non empty string! error, or uploading using bin/cake storage store doesn't generate full_path or url fields.

Gmail has a nice little hover state when dragging mail attachments into a new message. It looks like this:

I know there is already a black border when a file is dragged over, but perhaps the Media Manager could benefit from a

Currently, there is no way to cleanly destroy a Widget from the DOM, which is critical in SPA setups.

The functionality exists, however, in the form of a cleanup() method:

https://github.com/uploadcare/uploadcare-bower/blob/master/uploadcare.js#L8075

But since it's wrapped in a closure, it is not publicly exposed. I think there should be a destroy method on a Widget instance to handle this

The docs have a page on uploading files to S3, but there's no live example.

A live example might require an S3 bucket with public write access, or a publicly accessible endpoint that hands out presigned upload URLs.

RDU makes uploading files to S3 almost trivial, but this isn't so apparent without a live example.

Also, it would be good to

The docs (https://github.com/filestack/filestack-js/blob/6987bc691d861296a8f3b186ae90a1f69fd4d230/src/lib/picker.ts#L223) say that the files are passed to the onError callback, is that correct? If so, how does one get any information about the error that occurred?