You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Stammdaten: a personnel row without a Nachname is silently dropped on save #650
That list feeds Personnel = _personnel.ToPeople() (MasterDataEditorViewModel.cs:293). SPEICHERN reports success, and the row — Vorname, phone, Funkrufname, e-mail and all — is gone the next time the editor opens. Nothing on screen says so. Someone entering a new Einsatzkraft who fills the Vorname first and moves on loses the whole row.
Expected
A row that has any field filled but no Nachname is a conflict, raised in RefreshPersonnelConflicts the same way the e-mail conflict is: the banner names the row (e.g. "Person ohne Nachname: Zeile 4") and SPEICHERN stays disabled until it is fixed.
A completely empty row may still be dropped silently; that is an untouched blank, not data.
Notes
Bug fix: write the failing test first — fill only the Vorname, assert SPEICHERN is blocked and the conflict text names the row.
This touches the UI, so the PR needs a before/after screenshot pair.
Activity