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

feat(rückmeldung): "ILS" is hardcoded — including in the ETB entry written to the incident file

Open
  • Is something wrong?
#400 1 comment 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
Mostly clear
Activity status
Active
Tech stack
csharp, sqlite
Domain
backend-api-design, database

Research direction

Read #350 first to understand the project’s decision about persisted German wording. The issue identifies IncidentWorkspaceView.axaml:170, MasterDataEditorView.axaml:74,80, ReminderViewModel.cs:121, IncidentSettings, and etb_entries; trace how settings and ETB entries are stored and displayed. Done means the dispatch label is configurable in both labels and ETB records, consistent with the decision for old and new files.

Written by the indexing model from the issue text.

Description

enhancement i18n

From a portability review of main (ecb341b).

The gap

"ILS" — Integrierte Leitstelle — is the Bavarian name for the dispatch centre. Elsewhere in Germany the counterpart is a Kreisleitstelle, Rettungsleitstelle or plain Leitstelle; in Austria it is a Landeswarnzentrale or Bezirksalarmzentrale. The word is hardcoded in three places:

  • the workspace button — src/LageBuch.App.Shared/Views/IncidentWorkspaceView.axaml:170
  • the two settings labels — src/LageBuch.App.Shared/Views/MasterDataEditorView.axaml:74,80
  • the ETB entry written into the incident file — src/LageBuch.AppLogic/ViewModels/ReminderViewModel.cs:121:
EtbDirection.Outgoing, "Rückmeldung an ILS", from: _session.Operator?.CallSign, to: "ILS");

The first two are labels. The third is data: it lands in etb_entries.text and etb_entries.to and stays there for the life of the file.

Why this one is worth thinking about rather than just renaming

Everything else a brigade would recognise as local vocabulary is already master data — roles, vehicle status, Trupp types, call signs, checklists. StammdatenCatalogue never rejects an unknown value. The dispatch counterparty is the one operational concept the app names for you.

A string in IncidentSettings (md_settings, alongside ils_reminder_interval_minutes) covers the two labels cheaply. The ETB entry is the interesting half, because writing the configured label into the file makes the record locally correct but the file no longer self-describing, while writing a stable key and rendering the label at display time means old files and new files disagree about what they contain.

That is the same question #350 has to answer for every other piece of German wording the domain persists, so this issue should probably wait on that decision rather than pre-empt it — but the dispatch label is a good concrete test case for whatever gets decided, because unlike "Einsatz begonnen" it genuinely varies between installs within Germany.

Scope note

The ils_number column in incident_meta is unrelated legacy — a retired second number merged back into the Einsatznummer on load (IncidentRepository.cs:633-639). Not part of this.

Dominant language
C#
Stars
1
Forks
3
Avg merge
4h 15m
Merged PRs (30d)
181

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.