Cldr Currencies version 2.8.0

Enhancements

• Add support for CLDR 38

Cldr Currencies version 2.8.0-rc.0

Enhancements

• Add support for CLDR 38

Cldr Currencies version 2.7.0

Enhancements

• Use Cldr.default_backend!/0 when available since Cldr.default_backend/0 is deprecated as of ex_cldr version 2.18.0

Cldr Currencies version 2.6.2

Bug Fixes

• Uses Supervisor.child_spec/2 for eternal workers to remove deprecation warning on Elixir 1.11

Cldr Currencies version 2.6.1

Bug Fixes

• Make dialyzer happy. The @specs for Cldr.Eternal.start_link/1 and Cldr.Eternal.start_link/0 however remain a mystery and are commented out for now - success typing seems happy nevertheless.

Cldr Currencies version 2.6.0

Breaking change

• Remove Cldr.Currency.make_currency_code/1 whose need is replaced by Cldr.validate_currency/1.

Deprecations

• Deprecate Cldr.Currency.known_currency?/1 in favour of Cldr.Currency.known_currency_code?/1

• Deprecate Cldr.Currency.known_currencies/0 in favour of Cldr.Currency.known_currency_codes/0

Enhancements

• Support the creation of private use currencies with Cldr.Currency.new/2. Newly created private use currencies are stored in an :ets table which means that currencies will need to be recreated on each application restart. Creating the currencies is a developer responsibility although this may change in the future. In order to create currencies a supervisor and :ets table owner must be started. See the README for further details on adding the private use currency store to your application supervision tree.

• Add :alt_code to the Cldr.Currency struct. When creating a new currency, the currency code must conform to ISO4217 meaning that any new code must be in the "private use" range. This in turn means that the currency code must start with "X" and be three characters long. Many crypto currencies have either conflicting currency codes (do not comply with ISO4217 private use) or are invalid codes (longer than three characters). The :alt_code can be used to store an arbitrary alternative currency code than can be used to identify cryptocurrencies by a more familiar code.

Cldr Currencies version 2.5.0

Enhancements

• Add Cldr.Currency.currency_from_locale/{1, 2}

• Add Cldr.Currency.current_currency_from_locale/1

• Add Cldr.Currency.current_currency_from_territory/1

• Add Cldr.Currency.currency_format_from_locale/1

• Add <backend>.currency_from_locale/{1, 2}

Cldr Currencies version 2.5.0-rc.0

Enhancements

• Add Cldr.Currency.currency_from_locale/{1, 2}

• Add Cldr.Currency.current_currency_from_locale/1

• Add Cldr.Currency.current_currency_from_territory/1

• Add Cldr.Currency.currency_format_from_locale/1

• Add <backend>.currency_from_locale/{1, 2}

Cldr Currencies version 2.4.1

Bug Fixes

• In some rare cases, currency strings have a trailing .. These are now removed when producing currency strings that are used for parsing money amounts in ex_money.

Cldr Currencies version 2.4.0

Enhancements

• Adds the options :only and :except to Cldr.Currency.filter_currencies/3. These options are exercised in ex_money in the Money.parse/2 function to limited parsed user input to a particular set of currencies.