Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

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

未关闭
#400 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
csharp, sqlite

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
C#
星标
1
派生
3
平均合并
4 小时 15 分钟
30 天内合并 PR
181

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

CodeForFire/lagebuch 的其他 Issue

查看 CodeForFire/lagebuch 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。