Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Municipality field is mandatory of JP address

Open
#244 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Domain
localization

Research direction

Locate the Japanese address-format definition and compare its current fmt, lfmt, and require values with the issue's expected values. Verify that municipality (C) appears in the formatted address and that the required-field sequence includes C, producing the listed Japanese address levels in the correct order.

Written by the indexing model from the issue text.

Description

In the Japanese address system, the name of the municipality shown below is required on the second level of the address.

  • Cities (e.g. 横浜市, city in Kanagawa Pref.)
  • Towns with county names (e.g. 乙訓郡大山崎町, town in Kyoto pref.)
  • Villages with county names (e.g. 南河内郡千早赤阪村, village in Osaka pref.)
  • Special wards in the Tokyo metropolis (e.g. 渋谷区, Special ward in Tokyo metropolis)

Actual:
fmt: "〒%Z%n%S%n%A%n%O%n%N"
lfmt: "%N%n%O%n%A, %S%n%Z"
require: "ASZ"

Expected:
fmt: "〒%Z%n%S%n%C%n%A%n%O%n%N"
lfmt: "%N%n%O%n%A, %C, %S%n%Z"
require: "ACSZ"

Dominant language
C++
Stars
629
Forks
109
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from google/libaddressinput

All issues in google/libaddressinput

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.