You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,10 @@
1
1
# TransloaditKit Changelog
2
2
3
+
## Next
4
+
5
+
* Added `tusUploadChunkSize` to Transloadit initializers so apps can tune TUS chunking behavior, including single-request uploads with `0`.
6
+
* Clarified that `createAssembly(... andUpload ..., completion:)` completes after upload scheduling, not after file upload or processing completion.
7
+
3
8
## 3.5.0
4
9
5
10
* Allow clients to inject only an api key and provide a signature generator closure to calculate signatures for signing requests instead of injecting a key and secret. ([#42](https://github.com/transloadit/TransloaditKit/issues/42))
@@ -34,7 +39,7 @@
34
39
### Fixes
35
40
36
41
### Added
37
-
* It's now possible to cancel a running Assembly
42
+
* It's now possible to cancel a running Assembly
38
43
* Bumped TUSKit version
39
44
* Allow passing of custom fields to assembly creating by passing them to `createAssembly` methods
The generator itself is passed a string that needs to be signed (a JSON representation of the request parameters that you're generating a signature for) and a closure that you _must_ call to inform the SDK when you're done generating the signature (whether it's successful or failed).
65
65
66
-
**Important** if you don't call the completion handler, your requests will never be sent. The SDK does not implement a fallback or timeout.
66
+
**Important** if you don't call the completion handler, your requests will never be sent. The SDK does not implement a fallback or timeout.
67
67
68
68
The SDK will invoke the signature generator for every request that requires a signature. It will pass a parameter string for each request to your closure which you can then send to your service (local or external) for signature generation.
69
69
@@ -73,6 +73,18 @@ To learn more about signature generation see this page: https://transloadit.com/
73
73
74
74
To create an `Assembly` you invoke `createAssembly(steps:andUpload:completion)` on `Transloadit`.
75
75
It returns a `TransloaditPoller` that you can use to poll for the `AssemblyStatus` of your `Assembly`.
76
+
The completion handler is called after the Assembly has been created and uploads have been scheduled. It does not mean the files have finished uploading.
77
+
Use `TransloaditFileDelegate.didFinishUpload` to detect file upload completion, and use the returned poller to wait for processing completion.
78
+
79
+
By default, TUS uploads are split into 500 KiB chunks. For iOS background uploads, this means the system needs to schedule a new upload task for every chunk.
80
+
If that is too aggressive for your app, configure a larger `tusUploadChunkSize`, or pass `0` to let TUSKit upload each file in one request:
0 commit comments