Multiple file upload plugin with image previews, drag and drop, progress bars. S3 and Azure support, image scaling, form support, chunking, resume, pause, and tons of other features.
This release only affects TypeScript users as the TypeScript definitions file has now been updated to support module import in TypeScript and Angular 2 based projects. Documentation has been updated to demonstrate this release at https://docs.fineuploader.com/branch/master/features/modules.html
See #1840 to learn more about changes to TypeScript definitions file
This issue/fix only affects Fine Uploader S3.
Reported in #1852 and fixed in #1859.
No code changes - see 5.14.3 release for the most recent code changes.
Details in #1830. Also updated README.md w/ Open Collective sponsorship details.
onStatusChange is called w/ a status of qq.status.UPLOAD_SUCCESSFUL for initial/canned files before internal state for the file is completely updated. This change introduces an update that makes it easy for internal users of the upload-data service to defer the status change broadcast until all processing and state updates are complete.
re:
Fixed in #1759. Just an update to the TypeScript definition file. Non-TypeScript users are not affected at all by this release.
A comprehensive TypeScript definition file that covers the entire API is not included in the build output. TypeScript users will now be able to benefit from type-checking when working with Fine Uploader in a TypeScript environment. The package.json file has been updated appropriately so TypeScript should be able to discover the definition file without issue. If you are already using the definitions on DefinitelyTyped, please switch to the definitions bundled with the library as the DefinitelyTyped records will be removed/deprecated in the near future. See #1719 for more details on implementation of this integration.
setStatus(id, newStatus)Initially, only qq.status.DELETED and qq.status.DELETE_FAILED are supported. All other statuses will throw a qq.Error. This can be used to mark a file as deleted, or to indicate that a delete attempt failed if you are using delete file logic outside of Fine Uploader's control. This will update the UI by removing the file if you are using Fine Uploader UI as well.
For example:
// marks file with ID of 3 as deleted
uploader.setStatus(3, qq.status.DELETED)
Docs at http://docs.fineuploader.com/branch/develop/api/methods.html#setStatus
re:
removeFileRef(id)Documented at http://docs.fineuploader.com/branch/develop/api/methods.html#removeFileRef.
This allows you to free any memory associated with a client-side generated Blob. This is something you might want to do after the file has been successfully uploaded. For example:
var uploader = new qq.FineUploaderBasic({
request: {
endpoint: '/my/upload/endpoint'
},
callbacks: {
onComplete: function(id, name, response) {
if (response.success && this.getFile(id).inMemoryBlob) {
this.removeFileRef(id)
}
}
}
})
// elsewhere
var someBlobCreatedClientSide = createBlob(...)
someBlobCreatedClientSide.inMemoryBlob = true
uploader.addFiles(someBlobCreatedClientSide)
re: #1711
Makefile was updated to ensure builds execute correctly in a Windows/Cygwin environment. More details in #1698.A comprehensive TypeScript definition file that covers the entire API is not included in the build output. TypeScript users will now be able to benefit from type-checking when working with Fine Uploader in a TypeScript environment. The package.json file has been updated appropriately so TypeScript should be able to discover the definition file without issue. If you are already using the definitions on DefinitelyTyped, please switch to the definitions bundled with the library as the DefinitelyTyped records will be removed/deprecated in the near future. See #1719 for more details on implementation of this integration.
Also, the Makefile was updated to ensure builds execute correctly in a Windows/Cygwin environment. More details in #1698.
Docs at http://docs.fineuploader.com/branch/develop/api/methods.html#setStatus
Initially, only qq.status.DELETED and qq.status.DELETE_FAILED are supported. All other statuses will throw a qq.Error. This can be used to mark a file as deleted, or to indicate that a delete attempt failed if you are using delete file logic outside of Fine Uploader's control. This will update the UI by removing the file if you are using Fine Uploader UI as well.
For example:
// marks file with ID of 3 as deleted
uploader.setStatus(3, qq.status.DELETED)
re:
Documented at http://docs.fineuploader.com/branch/develop/api/methods.html#removeFileRef.
This allows you to free any memory associated with a client-side generated Blob. This is something you might want to do after the file has been successfully uploaded. For example:
var uploader = new qq.FineUploaderBasic({
request: {
endpoint: '/my/upload/endpoint'
},
callbacks: {
onComplete: function(id, name, response) {
if (response.success && this.getFile(id).inMemoryBlob) {
this.removeFileRef(id)
}
}
}
})
// elsewhere
var someBlobCreatedClientSide = createBlob(...)
someBlobCreatedClientSide.inMemoryBlob = true
uploader.addFiles(someBlobCreatedClientSide)
re: #1711