Skip to content

Update to CLDR 48 data - #51

Merged
Schultzer merged 1 commit into
mainfrom
cldr48
Nov 5, 2025
Merged

Schultzer merged 1 commit into
mainfrom
cldr48

Conversation

@kipcole9

@kipcole9 kipcole9 commented Nov 5, 2025

Copy link
Copy Markdown
Collaborator

This PR provides minimal updates to support the upcoming ex_cldr version 2.44.0 that itself is updated for CLDR 48.

The primary change - which needs review - is to the flag_exists?/1 function which relied upon all mapped territories having children. With the new data that is no longer a valid assumption. There may be a better workaround than contained in this PR.

@Schultzer

Copy link
Copy Markdown
Collaborator

This PR provides minimal updates to support the upcoming ex_cldr version 2.44.0 that itself is updated for CLDR 48.

The primary change - which needs review - is to the flag_exists?/1 function which relied upon all mapped territories having children. With the new data that is no longer a valid assumption. There may be a better workaround than contained in this PR.

The flag_exists?/1 function might benefit by a dedicated recursive function, but I don’t see that as a blocker, we can just leave that open for any contribution.

It looks like the CI is failing I’ll have a look at that tomorrow before I merge an release!

@kipcole9

kipcole9 commented Nov 5, 2025

Copy link
Copy Markdown
Collaborator Author

I think the CI issue is because I pushed the PR before I published the ex_cldr update. So should be ok when it's re-run. (I've published all the updates on my side for CLDR 48).

@Schultzer
Schultzer merged commit 2dfe46a into main Nov 5, 2025
2 of 4 checks passed
@Schultzer
Schultzer deleted the cldr48 branch November 5, 2025 23:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants