|
|
@@ -86,7 +86,7 @@ What we need to do to release Uppy 1.0
|
|
|
- [ ] core: research !important styles to be immune to any environment/page. Maybe use smth like `postcss-safe-important`. Or increase specificity (with .Uppy) (@arturi)
|
|
|
- [ ] test: add https://github.com/pa11y/pa11y for automated accessibility testing (@arturi)
|
|
|
- [ ] test: add tests for `npm install uppy` and running in different browsers, the real world use case (@arturi)
|
|
|
-- [ ] core: Uppy ID per instance
|
|
|
+- [x] core: Uppy ID per instance (@goto-bus-stop)
|
|
|
- [ ] core: allow setting custom `id` for plugins: https://github.com/transloadit/uppy/pull/328#issuecomment-328242214 (@arturi)
|
|
|
- [ ] core: move `setPluginState` to Plugin class ? (@goto-bus-stop)
|
|
|
- [ ] add `FormEncapsulator`: a plugin that is used in conjunction with any other acquirer, responsible for injecting any result (like from Transloadit plugin) back into the form (jquery-sdk includes the whole Assembly Status JSON in a hidden field i think)
|
Renée Kooi