Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Make admin1 required in Australia and Turkey

未关闭
#211 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
52/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
领域
localization

调研方向

检查 Australia 和 Turkey 的国家格式文件,然后将其与 issue 中讨论的 Malaysia、Argentina 和 Ireland 案例进行比较。更新 Australia 和 Turkey 的 admin1 必填要求,同时保持比较案例不变;完成的标准是这两个国家要求 admin1,且其他检查过的格式保留当前行为。

由索引模型根据 Issue 内容生成。

描述

I believe that admin level 1 should be required for the following countries, even though they are currently optional in the format files.

Australia. See https://auspost.com.au/sending/check-sending-guidelines/addressing-guidelines for the postal guidelines: "The last line should contain the place name or post office of delivery, state or territory abbreviation and postcode. This line should be printed in capitals without punctuation or underlining, with the postcode put last.".

Turkey. See https://docs.informatica.com/data-as-a-service/address-verification/h2l/address-verification-best-practices-for-turkey/address-verification-best-practices-for-turkey/key-address-elements.html

I have also checked every other country in the data set where admin1 is supported but optional. I think it's just the following three, and they look correct to me.

Malaysia. The examples on https://www.pos.com.my/business/business-mail-solutions/products/standard-mail.html include some with the province written and some without it.

Argentina. See https://docs.informatica.com/data-as-a-service/address-verification/h2l/address-verification-best-practices-for-argentina/address-verification-best-practices-for-argentina/key-address-elements.html.

Ireland. See https://correctaddress.anpost.ie/pages/Search.aspx, where the county should be shown on an envelope "where required". That implies it is not always required. As a concrete example where that is true, addresses in Dublin frequently leave off the "Co. Dublin" when formatting the address.

主要语言
C++
星标
629
派生
109
PR 合并指标
30 天内没有已合并 PR

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

google/libaddressinput 的其他 Issue

查看 google/libaddressinput 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。