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

feat(incident-data): autocomplete for street and Ortsteil

Open
#461 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
csharp, json
Domain
database, frontend

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

enhancement

Field feedback

„einsatzdaten: autocomplete strasse / ortsteil“

Today

  • STRASSE and ORTSTEIL are plain TextBoxes (src/LageBuch.App.Shared/Views/IncidentDataDialogView.axaml:20-36), saved via SetAddress(street, district).
  • MasterDataSet has 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.json and the FFB master-data repo.
Dominant language
C#
Stars
1
Forks
3
Avg merge
4h 34m
Merged PRs (30d)
182

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 CodeForFire/lagebuch

All issues in CodeForFire/lagebuch

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.