Releases: vivekmunde/ember-m-image
Releases · vivekmunde/ember-m-image
v1.0.0
Release Notes
Dependency Inversion
The m-image
component now accepts a loader
param which accepts a loader function, which is used to download the image from the source, e.g. through ajax / fetch call. This param can be supplied with any custom loader as well.
In previous version, the component m-image
was tightly coupled with image loaders. This was stopping the component to scale to accept any external custom loader.
Fetch Approach
Fetch API approach to download the image from source.
Parameters Update
- Parameter
imageSrc
has been replaced bysrc
- Parameter
errorImageSrc
has been replaced byfallbackImageSrc
- Parameters
useAjax
,encodeToBase64
&ajaxOptions
have been removed - New parameter
loader
has been introduced
v0.1.5
Release Notes
- Documentation update
v0.1.4
Release Notes
- DOM Approach: Replaced the creation of actual temporary DOM
<img>
tag insidebody
, using jQuery, by the standard javascript constructorImage()
and the standard DOM element methods EventTarget.addEventListener and EventTarget.removeEventListener. Now it creates in memory temporary DOM Image and destroys after its use. There are no changes on the control level API front with this update. - AJAX Approach: Introduced a new control level API parameter
ajaxOptions
which can be used to supply the jQuery AJAX options
v0.1.3
Release Notes
- DOM Approach: Along with the AJAX Approach (released in v0.1.2), this release includes a new DOM Approach to download the image
- Documentation update
Forward Compatibility
- AJAX Approach: v0.1.3 uses the DOM Approach by default. So when migrating from v0.1.2 to v0.1.3, if you want to use AJAX Approach then set the
useAjax
flag totrue
for the component{{m-image}}
.
v0.1.2
Release Notes
- AJAX Approach: This release introduces the jQuery AJAX approach to download the image from the source