feat(incident-data): autocomplete for street and Ortsteil
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start with src/LageBuch.App.Shared/Views/IncidentDataDialogView.axaml:20-36 and inspect how the existing Zugeteilt AutoCompleteBox is populated; then read the MasterDataSet and SetAddress definitions. The issue leaves the data source and its relationship to work in #401, #420 and #427 undecided, so those questions need resolution before implementation. Done means both fields support autocomplete, free text remains allowed, and an unambiguous street selection fills its Ortsteil; the example JSON and FFB master-data repository are updated.
Written by the indexing model from the issue text.
Description
Field feedback
„einsatzdaten: autocomplete strasse / ortsteil“
Today
- STRASSE and ORTSTEIL are plain
TextBoxes (src/LageBuch.App.Shared/Views/IncidentDataDialogView.axaml:20-36), saved viaSetAddress(street, district). MasterDataSethas no list of streets or Ortsteile.
Proposal
- New master-data categories: Ortsteile, and streets (optionally linked to an Ortsteil).
- Both fields become
AutoCompleteBoxes, like Zugeteilt. - Picking a street fills in its Ortsteil when that is unambiguous.
- Free text stays allowed.
Open questions
- Where do the lists come from: entered by hand, or imported (for example an OSM/CSV export for the municipality)?
- How does this fit with #401 (address model lacks house number, PLZ and Ort) and #420/#427 (address/object entity in master data)? Streets should be the same entity as those, not a third one.
- Schema change: update
docs/master-data.example.jsonand the FFB master-data repo.
- Dominant language
- C#
- Stars
- 1
- Forks
- 3
- Avg merge
- 4h 34m
- Merged PRs (30d)
- 182
Getting set up
- No Dockerfile or Docker Compose file
- Has a 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 CodeForFire/lagebuch
-
bug ux
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
CodeForFire/lagebuch#714 ·
Maintainers usually reply within 1 day
-
bug ux
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
CodeForFire/lagebuch#713 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
CodeForFire/lagebuch#405 ·
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
CodeForFire/lagebuch#349 ·
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
CodeForFire/lagebuch#348 ·
Maintainers usually reply within 1 day
All issues in CodeForFire/lagebuch
Similar issues
-
[BUG]: Position intent set on a simple order is dropped when it becomes a bracket, OCO or OTO orderPossibly taken @RaphaelFakhri claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
alpacahq/alpaca-trade-api-csharp#903 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
joinrpg/joinrpg-net#5752 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
dimitar-radenkov/Pointframe#294 ·
Maintainers usually reply within 1 day
-
kind/feature-request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Altinn/altinn-correspondence#2154 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
Okabintaro/SubmersedVR#253 ·