Releases: elixir-cldr/cldr_units
Cldr Units version 2.5.2
Bug Fixes
-
Replace
Cldr.get_current_locale/0
withCldr.get_locale/0
in docs -
Fix dialyzer warnings
Cldr Units version 2.5.1
Enhancements
-
Standardize the development cldr backend as
MyApp.Cldr
which makes for more understandable and readable examples and doc tests -
Cldr.Unit.to_string/3
now allows for thebackend
parameter to default toCldr.default_backend/0
-
Correct the implementation of option
:style
that is other than:long
Cldr Units version 2.5.0
Enhancements
- Updates to CLDR version 35.0.0 released on March 27th 2019.
Cldr Units version 2.4.0
Enhancements
- Supports
Cldr.default_backend()
as a default forbackend
parameters inCldr.Unit
Cldr Units version 2.3.2
Bug Fixes
- Fix dialyzer warnings
Cldr Units version 2.3.1
Enhancements
- Makes generation of documentation for backend modules optional. This is implemented by the
:generate_docs
option to the backend configuration. The default istrue
. For example:
defmodule MyApp.Cldr do
use Cldr,
default_locale: "en-001",
locales: ["en", "ja"],
gettext: MyApp.Gettext,
generate_docs: false
end
Cldr Units version 2.3.0
Enhancements
- The conversion tables are now stored as json and updates may be downloaded at any time with the mix task
mix cldr.unit.download
. This means that updates to the conversion table may be made without requiring a new release ofCldr.Unit
.
Cldr Units version 2.2.0
Enhancements
This release is primarily about improving the conversion of units without introducing precision errors that accumulate for floats. The strategy is to define the conversion value between individual unit pairs.
Currently the implementation uses a static map. In order to give users a better experience a future release will allow for both specifying mappings as a parameter to Cldr.Unit.convert/2
and as compile time configuration options including the option to download conversion tables from the internet.
-
Direct conversions are now supported. For some calculations, the process of diving and multiplying by conversion factors produces an unexpected result. Some direct conversions are now defined which produce a more expected result.
-
In most cases, return integer values from conversion and decomposition when the originating unit value is also an integer
Cldr Units version 2.1.0
Enhancements
-
Add
Cldr.Unit.Conversion.convert!/3
-
Add
Cldr.Unit.Math.cmp/2
-
Add
Cldr.Unit.decompose/2
-
Add
Cldr.Unit.zero/1
-
Add
Cldr.Unit.zero?/1
The appropriate backend equivalents are also added.
Cldr Units version 2.0.0
Breaking changes
-
Cldr.Unit
now requires aCldr
backend module to be configured -
In order for the
String.Chars
protocol to be supported (which is used in string interpolation and byKernel.to_string/1
) a default backend must be configured. For example inconfig.exs
:
config :ex_cldr_units,
default_backend: MyApp.Cldr
Enhancements
- Move to a backend module structure with ex_cldr version 2.0