Releases: FineUploader/react-fine-uploader
Finally! v1.0.0 is out!
No changes since 1.0.0-rc2, other than an upgrade to [email protected], which itself hasn't changed since React Fine Uploader 1.0.0-rc2.
1.0 Release Candidate #2
Breaking change
Upgrade to fine-uploader-wrappers 1.0.0-rc2. See details at https://github.com/FineUploader/fine-uploader-wrappers/releases/tag/1.0.0-rc2.
Bug fix
onStatusChange
called to early for canned/initial files. Solved in Fine Uploader 5.14.2, which is a peerDependency in fine-uploader-wrappers 1.0.0-rc2.
re:
1.0 Release Candidate #1
Pulled in fine-uploader-wrappers v1.0.0-rc1.
Allow customResizer to be passed to <Thumbnail />
This allows a 3rd-party resizing library to be used (such as Pica) to resize thumbnail previews. This can be done with direct use of <Thumbnail />
or indirectly, though the <Gallery />
component. See the code demo at the end of the <Thumbnail />
component in the README for more details.
Completed in #24. This marks the last planned feature before v1.0.
Make use of newly exposed qq namespace
This required an updated to fine-uploader-wrappers v0.2.0, which exposed the entire qq
namespace on all uploader instances.
Benefits realized in React Fine Uploader:
- Delegated to built-in file/folder drop support detection.
- No more hardcoded status values - now delegate to
qq.status
.
Fix PropType for <Dropzone /> + lots of devDependency updates
Fixes the PropType for dropzone components element option. It expects a DOM node, which is an object. See #79 for details.
Support for initial file / canned file thumbnail previews
Now, thumbnails associated with initial files will be properly rendered both when using the <Gallery />
component and the lower-level <Thumbnail />
component (which the <Gallery />
uses internally. Specific changes include:
- New
fromServer
property available on<Thumbnail />
. <Gallery />
will attempt to render the<Thumbnail />
for an initial file using the image URL associated with the corresponding initial file record.
Breaking Changes: Wrapper classes moved to external package
All wrapper classes were moved to the fine-uploader-wrappers project. React Fine Uploader now depends on fine-uploader-wrappers.
Breaking changes:
Traditional, S3, and Azure wrappers must be imported from 'fine-uploader-wrappers'
You must now import the wrapper classes as follows:
- Traditional -
import FineUploaderTraditional from 'fine-uploader-wrappers'
- S3 -
import FineUploaderS3 from 'fine-uploader-wrappers/s3'
- Azure -
import FineUploaderAzure from 'fine-uploader-wrappers/azure'
Components are now at the root of the package
Instead of import FileInput from 'react-fine-uploader/components/file-input'
, you would pull in the <FileInput />
component as import FileInput from 'react-fine-uploader/file-input'
. All components have moved up one level - the 'components' folder is no more.
Also, <Gallery />
is now the default export for this package. It can be imported as import Gallery from 'react-fine-uploader'
.
re: #21
Breaking Change: No more require('*.css') in exported components
This is a breaking change release that addresses issues discussed in #50.
If you are migrating from a pre 0.4.0 release, you only need to make changes to your code if you were using the <Gallery />
component. If you are using <Gallery />
, you must now explicitly load/import the gallery.css file.
For example, if you are using Webpack or another bundler that is configured to allow CSS files to be imported, you will need to include be sure, in addition to the gallery.js
file, you also `import 'react-fine-uploader/components/gallery/gallery.css'.
If you are not using Webpack or a bundler, or if you do not want to or are not able to use ES6 imports to load CSS files, you must load the gallery.css
file using a <link>
tag instead.