Skip to content

Instantly share code, notes, and snippets.

@rxaviers

rxaviers/README.md

Created July 14, 2015 23:52
Show Gist options
  • Save rxaviers/fbca34ead79440b7f16f to your computer and use it in GitHub Desktop.
Save rxaviers/fbca34ead79440b7f16f to your computer and use it in GitHub Desktop.
Download ZIP
Raw
README.md

See comments.

@rxaviers
Copy link
Author

I will certainly consider open sourcing the integration;

Awesome. Please, keep me posted on its progress.

figuring out a "default" currency to use for a given locale

http://www.unicode.org/reports/tr35/tr35-numbers.html#Supplemental_Currency_Data

supplemental/currencyData.json has a region mapping with currencies. You can use that data to figure out the default currency of a region.

I think that

This could live in Globalize. Needs a good API. Feel free to submit an issue proposing one. Take into account http://www.unicode.org/reports/tr35/tr35-numbers.html#Currencies

and a better locale to bundle mapping

This could live in cldrjs. Needs a good API.

A way to manage currencies

@dpolivy
Copy link

dpolivy commented Jul 15, 2015

Alternatively, simply don't worry about it when we land (if we land) our built-in cache support. Currently implemented on globalizejs/globalize#436.

Do you have any timeline on when this might be incorporated?

@rxaviers
Copy link
Author

Good question :P, I've created an exclusive PR for cache support globalizejs/globalize#470 (I've decoupled it from 436)

@rxaviers
Copy link
Author

The cache support depends on PR#436 and I hope we're close to land it. So, basically we should decide if the benefits of the cache support outweigh its addition.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment