Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#400 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
csharp, sqlite
Área
backend-api-design, database

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
C#
Estrellas
1
Forks
3
Merge medio
4 h 34 min
PR fusionados (30 d)
182

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de CodeForFire/lagebuch

Todos los issues de CodeForFire/lagebuch

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.