feat(forms): per-field description texts (Erläuterungssätze) #81
No reviewers
Labels
No labels
bug
discussion
enhancement
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
edufeed/edufeed-app!81
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/field-descriptions"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adds an optional per-field description in the builder, stored in the field tag's open JSON settings bag, rendered under the label at fill time. Edit round-trip proven for ALL eight options-bag keys (the next silently dropped property fails by name), plus an e2e driving both fieldToState call sites including an XSS-inert check (FieldsRenderer interpolates, never {@html}).
TestOER-verified at
5c9ce139, no defects; output-wart scope measured (only field-output tags move, cycle converges with outputs pinned).Stacked on #78 (base: feat/issue-77-form-preview). Buzz thread: #edufeed-app.
🤖 Generated with Claude Code
FORMS_EDIT_ROUNDTRIP_SWEEP generalises the edit-direction guarantee from one property to the class: all eight options-bag keys driven through builder state -> tags -> parse -> fieldToState -> tags, tag sets asserted identical, so the NEXT dropped property fails too, not only description. Mutation-proven per property in TestOER's run; the displayIf row re-proven here against the files as landed (4 failed). E2E_FIELD_DESCRIPTION_EDIT drives both fieldToState call sites in a real browser — edit route and fork dialog — plus a hostile description (<img onerror>/<script>) asserted rendered as inert text: FieldsRenderer interpolates, never {@html}, measured not read. Written by TestOER, adopted verbatim; both files svelte-check clean (0 errors with them in), 3/3 e2e green on real Chrome here before committing.View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.