Releases: gicentre/elm-vegalite
1.3.0
Patch release
Minor additions to the API documentation.
1.2.0
Minor changes to bring in line with the release of Vega-Lite 3.0.0-rc12
Additions
- Four additional band scale confutation options for bars and rectangles:
sacoBarBandPaddingInner
,sacoBarBandPaddingOuter
,sacoRectBandPaddingInner
andsacoRectBandPaddingOuter
.
Minor:
- Updated all examples and test to use VegaLite3.0.0-rc12 runtime. Minor corrections/formatting of HTML in examples and tests.
Patch release
Improved scalability of programmatic data column generation.
No changes to the API, documentation or examples.
1.1.0
Minor changes to bring in line with the release of Vega-Lite 3.0.0-rc10
Additions
-
Add
fillOpacity
,strokeOpacity
andstrokeWidth
channels -
Add
monthdatehours
time unit -
New interaction examples demonstrating fillOpacity and strokeWidth channels and multi-line tooltip.
-
Errorbar test example using color encoding.
Documentation Changes
- Minor: Added Vega-Lite version badge to front page.
Patch Release
No API changes.
Bugs
- Corrected bug that prevented column spacing from being specified in a faceted view.
Documentation
- Minor change to example in documentation making reference to
elm-vegalite
rather thanelm-vega
Patch Release
Reduced asset size by using remote data in tests. No changes to API or documentation.
Patch release
Minor changes to documentation page banner
Patch release
Minor changes to API documentation
Release for Elm 0.19
For Elm 0.19 and above this release of what was formerly elm-vega (3.0) supports Vega-Lite only. For Vega support, see the now separate package elm-vega. No functionality has been lost in splitting the elmVega and elmVegaLite modules into separate packages, but the assets for each are now considerably smaller.
Changes to the API since earlier versions are just in replacing custom type constructors (like AFit
, and ANone
) with consistently named functions (asFit
and asNone
). This means that almost all custom type constructors are now replaced with equivalent functions that provide greater future-proofing as Vega-Lite evolves.
When updating legacy code, the Elm compiler should highlight which type constructors require replacing with their function equivalent. You can always find the mapping from types to functions in the Type Reference section at the end of the API documentation.