I’ve published ex_cldr version 2.47.0 that adds Cldr.Config.territory_codes/0. I’ve also opened a PR to ex_cldr_territories for @Schultzer to consider.
For now you can use the new function as:
@territory_codes Cldr.Config.territory_codes()
def territory_codes do
@territory_codes
end
The functions in Cldr.Config all read, decode and normalise data so you only want to do that once, at compile time, hence the module attribute approach.
Example
iex> Cldr.Config.territory_codes()
%{
EA: %{},
IM: %{alpha3: "IMN", numeric: "833"},
XG: %{alpha3: "XGG", numeric: "979"},
BH: %{alpha3: "BHR", fips10: "BA", numeric: "048"},
JM: %{alpha3: "JAM", numeric: "388"},
JO: %{alpha3: "JOR", numeric: "400"},
NC: %{alpha3: "NCL", numeric: "540"},
QO: %{alpha3: "QOO", numeric: "961"},
QU: %{alpha3: "QUU", numeric: "967"},
VN: %{alpha3: "VNM", fips10: "VM", numeric: "704"},
YE: %{alpha3: "YEM", fips10: "YM", numeric: "887"},
AG: %{alpha3: "ATG", fips10: "AC", numeric: "028"},
XE: %{alpha3: "XEE", numeric: "977"},
KR: %{alpha3: "KOR", fips10: "KS", numeric: "410"},
BD: %{alpha3: "BGD", fips10: "BG", numeric: "050"},
IT: %{alpha3: "ITA", numeric: "380"},
AD: %{alpha3: "AND", fips10: "AN", numeric: "020"},
SY: %{alpha3: "SYR", numeric: "760"},
SA: %{alpha3: "SAU", numeric: "682"},
SB: %{alpha3: "SLB", fips10: "BP", numeric: "090"},
AN: %{alpha3: "ANT", fips10: "NT", numeric: "530"},
NP: %{alpha3: "NPL", numeric: "524"},
XY: %{alpha3: "XYY", numeric: "997"},
BI: %{alpha3: "BDI", fips10: "BY", numeric: "108"},
PL: %{alpha3: "POL", numeric: "616"},
XA: %{alpha3: "XAA", numeric: "973"},
AO: %{alpha3: "AGO", numeric: "024"},
HT: %{alpha3: "HTI", fips10: "HA", numeric: "332"},
ML: %{alpha3: "MLI", numeric: "466"},
GY: %{alpha3: "GUY", numeric: "328"},
CH: %{...},
...
}