Skip to content

Cldr Currencies version 2.6.0
Compare
Choose a tag to compare
@kipcole9 kipcole9 released this 18 Jul 03:51
v2.6.0
dd9ccb4

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.

Assets 2
Loading