|
|
@@ -5,7 +5,7 @@ author: arturi
|
|
|
published: false
|
|
|
---
|
|
|
|
|
|
-Hi all! We are back from holidays with a shiny new `0.23.0` release for you! Its packed with a new `Url` plugin (imports files from urls), refactored `ThumbnailGenerator`, `Webcam` improvements and more.
|
|
|
+Hi all! We are back from holidays with a shiny new `0.23.0` release for you! It’s packed with a new `Url` plugin (imports files from urls), refactored `ThumbnailGenerator`, `Webcam` improvements and more.
|
|
|
|
|
|
## Import from Url
|
|
|
|
|
|
@@ -49,7 +49,7 @@ uppy.upload().then((result) => {
|
|
|
})
|
|
|
```
|
|
|
|
|
|
-You can still use events like `transloadit:result`, its just easier when things are in the same place. Plugins can use `uppy.addResultData()` API to add data to the `result`, like so:
|
|
|
+You can still use events like `transloadit:result`, its just easier when things are in the same place. Plugins can use new `uppy.addResultData()` API to add data to the `result`, like so:
|
|
|
|
|
|
```js
|
|
|
uppy.addResultData(uploadID, { transloadit: assemblies })
|
|
|
@@ -63,14 +63,9 @@ We’ve also added an option to select which camera will be used to capture pict
|
|
|
|
|
|
## Server
|
|
|
|
|
|
-- You can now specify a config path when starting the standalone Uppy-Server like so `uppy-server --config /path/to/uppyconf.json`. The config file is expected to be a json file with the same schema as the [uppy-server options](https://uppy.io/docs/server/#Options).
|
|
|
-- A periodic cleanup job has been added to uppy-server, to delete stale upload files from the specified `filePath`. Even though we'd rarely expect uploaded files to go undeleted immediately, there could be cases where an error occurs during an upload, and so uppy-server leaves the file undeleted to give room for upload retries. With the cleanup job in place, we can ensure that this file would eventually be deleted after the file upload is done.
|
|
|
-- Responses from Multipart uploads are now relayed to uppy client as they are received from the upload server. With this in place, you can now handle responses from local and remote XHRUpload in nearly the same way.
|
|
|
-
|
|
|
-## Misc
|
|
|
-
|
|
|
-- Third-party extension for integrating Ngrx Angular state management library with Uppy has been released, [uppy-store-ngrx](https://github.com/rimlin/uppy-store-ngrx/) by @rimlin.
|
|
|
-- Uppy releases are now hosted on Edgly CDN by Transloadit.
|
|
|
+- You can now specify a config path when starting the standalone Uppy Server like so `uppy-server --config /path/to/uppyconf.json`. The config file is expected to be a json file with the same schema as the [uppy-server options](https://uppy.io/docs/server/#Options).
|
|
|
+- A periodic cleanup job has been added to Uppy Server, to delete stale upload files from the specified `filePath`. Even though we'd rarely expect uploaded files to go undeleted immediately, there could be cases where an error occurs during an upload, and so uppy-server leaves the file undeleted to give room for upload retries. With the cleanup job in place, we can ensure that this file would eventually be deleted after the file upload is done.
|
|
|
+- Responses from Multipart uploads are now relayed to Uppy Client as they are received from the upload server. With this in place, you can now handle responses from local and remote XHRUpload in nearly the same way.
|
|
|
|
|
|
## Improvements
|
|
|
|
|
|
@@ -90,6 +85,11 @@ We’ve also added an option to select which camera will be used to capture pict
|
|
|
- Refactor provider views (#554 / @arturi)
|
|
|
- Lots of documentation fixes, thanks to all our contributers!
|
|
|
|
|
|
+## Misc
|
|
|
+
|
|
|
+- Third-party extension for integrating Ngrx Angular state management library with Uppy has been released, [uppy-store-ngrx](https://github.com/rimlin/uppy-store-ngrx/) by @rimlin.
|
|
|
+- Uppy releases are now hosted on Edgly CDN by Transloadit.
|
|
|
+
|
|
|
## Press
|
|
|
|
|
|
Uppy has made some appearances on the internet recently.
|
Artur Paikin