Should we have a `region` option instead of `locale`?
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 58
- Forks
- 12
- Avg merge
- 2h 35m
- Merged PRs (30d)
- 2
Description
For conversion every units.xml entry includes a 001 region, which means that the region of a valid locale will always be supported, and that therefore we will never fall back to a second-choice locale.
This raises the question of whether we should have a region option instead of a locale option, as the data is region-dependent rather than language-dependent.
Originally posted by @eemeli in https://github.com/tc39/proposal-amount/pull/110#discussion_r3895931758
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the region data in units.xml and the linked pull-request discussion that raised this question. Determine whether the public option should be region-based or remain locale-based, and consider the implications for locale fallback; done means an agreed API direction is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, internationalization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100