Erroneous sorting codes in French territories
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Domain
- localization
Research direction
Search the address-format data for the records for PM, YT, MC, WF, NC, MF, GP, GF, MQ, BL, and RE. Confirm each format string contains the reported %X code, remove those codes, and run the repository's relevant validation or tests if available to verify the affected formats.
Written by the indexing model from the issue text.
Description
The formats for PM YT MC WF NC MF GP GF MQ BL RE all erroneously include a %X sorting code.
They are all part of France, or for Monaco, a statelet whose post office is run by France. Both the French La Poste web site and the UPU confirm that they use standard French addresses with the five digit postal code before the city, no sorting code. For example, for PM https://www.upu.int/UPU/media/upu/PostalEntitiesFiles/addressingUnit/spmEn.pdf
It may have been confusing that for each territory the first three digits of its French code are fixed and only the last two vary within the territory, which might have been misinterpreted as a sorting code.
The fix is simple, remove all of the %X codes in each territory's format string.
- Dominant language
- C++
- Stars
- 629
- Forks
- 109
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from google/libaddressinput
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
google/libaddressinput#255 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
google/libaddressinput#245 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 64/100
google/libaddressinput#254 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 52/100
google/libaddressinput#250 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 58/100
google/libaddressinput#249 ·
All issues in google/libaddressinput
Similar issues
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
flashinfer-ai/flashinfer#6212 ·
Maintainers usually reply within 1 day
-
bug graphics
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
FlaxEngine/FlaxEngine#4295 · 2 comments ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Algorithmiq/monoprop#390 ·
Maintainers usually reply within 1 day
-
docs
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
8-membered-ring atrop stereo lost in 2026.09.1Possibly taken A pull request linked to this issue is open or already merged. Openbug
Difficulty 2/5 Half a day Newbie friendliness 86/100
Maintainers usually reply within 2 days