Skip to content
This repository was archived by the owner on Nov 20, 2018. It is now read-only.

Releases: FineUploader/fine-uploader

Overhaul of TypeScript definitions now allowing proper module import

Choose a tag to compare

@singhjusraj singhjusraj released this 27 Jul 02:46

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

Hotfix: Multi-part upload to S3 fails on Edge >= 15 with 403 Forbidden

Choose a tag to compare

@rnicholus rnicholus released this 27 Jun 03:31

This issue/fix only affects Fine Uploader S3.

Reported in #1852 and fixed in #1859.

Removed Open Collective from package.json/README.md

Choose a tag to compare

@rnicholus rnicholus released this 30 May 04:49

No code changes - see 5.14.3 release for the most recent code changes.

Hotfix: Update TypeScript definitions S3/Azure properties with default values to be optional

Choose a tag to compare

@rnicholus rnicholus released this 24 May 04:57

Details in #1830. Also updated README.md w/ Open Collective sponsorship details.

Hotfix: onStatusChange called to early for canned/initial files

Choose a tag to compare

@rnicholus rnicholus released this 06 Apr 04:03

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:

Hotfix: qq(element).clearText() missing TypeScript return value defintion

Choose a tag to compare

@rnicholus rnicholus released this 23 Feb 15:52

Fixed in #1759. Just an update to the TypeScript definition file. Non-TypeScript users are not affected at all by this release.

TypeScript support, setStatus via API, cleanup large Blobs in memory

Choose a tag to compare

@rnicholus rnicholus released this 17 Feb 05:11

Features

TypeScript support

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.

New API method - 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:

New API method - 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

Fixes

  • The Makefile was updated to ensure builds execute correctly in a Windows/Cygwin environment. More details in #1698.

TypeScript definition files + Windows build fix

Choose a tag to compare

@rnicholus rnicholus released this 13 Feb 02:59

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.

setStatus API method

setStatus API method Pre-release
Pre-release

Choose a tag to compare

@rnicholus rnicholus released this 02 Feb 03:08

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:

Added removeFileRef method

Pre-release

Choose a tag to compare

@rnicholus rnicholus released this 30 Jan 05:35

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