Hierarchical versions of admin and address fields (in different languages)?
Open
Nobody has claimed this yet.
glorious future
outreach
question
- Dominant language
- JavaScript
- Stars
- 6
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Description
The 'name' property is currently hierarchical and can contain several versions in different languages. Any plans to use the same approach systematically to all other relevant fields, such as country, county, locality and neighborhood? Zip, country, state etc. codes would not need this extension.
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 inspecting how the hierarchical name property is defined and how country, county, locality, and neighborhood fields are represented. Clarify which fields should support multilingual hierarchies and agree on the schema before changing the model; done means the scope and expected representation are documented and consistently defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100