|
|
@@ -116,6 +116,8 @@ What we need to do to release Uppy 1.0
|
|
|
- [ ] 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. See also https://github.com/transloadit/uppy/issues/750
|
|
|
- [x] statusbar: add some spacing between text elements (#760 / @goto-bus-stop)
|
|
|
+- [ ] core: use Browserslist config to share between PostCSS, Autoprefixer and Babel https://github.com/browserslist/browserslist, https://github.com/amilajack/eslint-plugin-compat (@arturi)
|
|
|
+- [ ] core: utilize https://github.com/jonathantneal/postcss-preset-env, maybe https://github.com/jonathantneal/postcss-normalize (@arturi)
|
|
|
- [ ] docs: improve on React docs https://uppy.io/docs/react/, add small example for each component maybe? Dashboard, DragDrop, ProgressBar? No need to make separate pages for all of them, just headings on the same page. Right now docs are confusing, because they focus on DashboardModal. Also problems with syntax highlight on https://uppy.io/docs/react/dashboard-modal/.
|
|
|
- [ ] docs: add note in docs or solve the .run() issue, see #756
|
|
|
- [x] core: add `uppy.getFiles()` method (@goto-bus-stop / #770)
|
Artur Paikin