feat(inputs): add labels and example placeholders to every input field - #143
Merged
Conversation
Issue #137 asks that every input field always show a visible label and that placeholders show anonymized example data instead of restating the label or giving an instruction. The Kraefte tab was the closest existing model, but only one field in the whole app actually followed the pattern; ~9 other views had the same gap in one direction or the other (missing labels, or placeholders that just repeat the label). - Add AnonymizedExampleData (Persistence/MasterData) as the single source of anonymized example values and "z. B. ..." placeholders, replacing three duplicated test fixtures. - Add a HeaderedContentControl.field style so a field structurally cannot be added without a visible label. - Apply labels + example placeholders across every view with input fields: Kraefte, Funktionen, ETB, Atemschutz, Aufgaben, CO-Messung, Dateien, the Stammdaten editor, and the operator join dialog. Free-text fields (Bemerkung, Eintrag, Aufgabe) intentionally get no placeholder. - Unify TasksView/TaskDialogView's separate "cellLabel" style into the same tracked-out label style used everywhere else. - Fix a stale KRAEFTE tab index in ForcesTabRenderTests (left over from when the AUFGABEN tab was inserted) so its screenshots show what they claim to. - Fix incidental UI bugs surfaced while reviewing screenshots: a hardcoded MinHeight on the Kraefte STATUS combo that made it shorter than every other input; inconsistent title-row vertical alignment across tabs; a missing CO-MESSPROTOKOLL title; CO-Messung's editor sidebar (spinner buttons on a field with no real min/max, a redundant close button next to an existing Abbrechen button, checkbox/label misalignment). - Add render-test coverage for Funktionen, ETB, and the Task dialog, which previously had none. Closes #137 Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EgFDVXVsJVKJAw1fxBETFR Signed-off-by: Thomas Müller <1005065+DeepDiver1975@users.noreply.github.com>
DeepDiver1975
force-pushed
the
feat/labeled-input-placeholders
branch
from
August 27, 2026 11:01
fedd800 to
362d1cf
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
z. B. ...) instead of one that restates the label or gives an instruction, per ui concept: always labels next to input fiels - placeholders show examples #137.AnonymizedExampleDataas the single source of example data (replacing duplicated test fixtures) and aHeaderedContentControl.fieldstyle so a field can't be added without a label.Test plan
dotnet test tests/LageBuch.AppLogic.Tests— 285 passedCloses #137
🤖 Generated with Claude Code
https://claude.ai/code/session_01EgFDVXVsJVKJAw1fxBETFR