|
@@ -110,6 +110,10 @@ What we need to do to release Uppy 1.0
|
|
|
- [ ] uppy-server: benchmarks / stress test, large file, uppy-server / tus / S3 (10 GB)
|
|
- [ ] uppy-server: benchmarks / stress test, large file, uppy-server / tus / S3 (10 GB)
|
|
|
- [ ] uppy-server: document docker image setup for uppy-server (@ifedapoolarewaju)
|
|
- [ ] uppy-server: document docker image setup for uppy-server (@ifedapoolarewaju)
|
|
|
- [ ] xhrupload: emit a final `upload-progress` event in the XHRUpload plugin just before firing `upload-complete` (tus-js-client already handles this internally) (@arturi)
|
|
- [ ] xhrupload: emit a final `upload-progress` event in the XHRUpload plugin just before firing `upload-complete` (tus-js-client already handles this internally) (@arturi)
|
|
|
|
|
+- [ ] core: add more mime-to-extension mappings from https://github.com/micnic/mime.json/blob/master/index.json (which ones?) (@arturi, @goto-bus-stop)
|
|
|
|
|
+- [ ] providers: select files only after “select” is pressed, don’t add them right away when they are checked (keep a list of fileIds in state?); better UI + solves issue with autoProceed uploading in background, which is weird; re-read https://github.com/transloadit/uppy/pull/419#issuecomment-345210519 (@arturi, @goto-bus-stop)
|
|
|
|
|
+- [ ] tus: add `filename` and `filetype`, so that tus servers knows what headers to set https://github.com/tus/tus-js-client/commit/ebc5189eac35956c9f975ead26de90c896dbe360
|
|
|
|
|
+- [ ] core: look into utilizing https://github.com/que-etc/resize-observer-polyfill for responsive components
|
|
|
|
|
|
|
|
## 0.24.0
|
|
## 0.24.0
|
|
|
|
|
|
Artur Paikin