getodk / getodk/web-forms

Improve the way errors are displayed in groups

Open
#482 0 comments 0 reactions 0 assignees View on GitHub
needs ui/ux design
Dominant language
TypeScript
Stars
38
Forks
22
PR merge metrics
No merged PRs in 30d

Description

### Description
QA identified that it could be helpful to highlight the group header/panel in addition to the individual fields that have validation issues. This would make it easier for users to quickly spot where problems exist, especially in larger forms.

### Design needs
Define how the panel header should be highlighted (e.g., red border, background, or icon).

Consider different states:

- If all fields in the group are invalid, should the entire header be red?
- If only one field is invalid, should the header still show an error state, or only the field itself?
- Ensure the design remains clear without overwhelming the user with too much red.

---

### Checklist
- **Does it need UI/UX design?**
- [ ] Yes. Describe the UI/UX requirements or attach a Figma link in the "Design" section.
- [ ] No
- **Does it need API design?**
- [ ] Yes. Specify the endpoints, methods, or data structures needed.
- [ ] No
- **Does it need design around state flow?**
- [ ] Yes. Outline the state flow requirements.
- [ ] No
- **Does it need a test plan?**
- [ ] Yes. Add the test plan as a comment in this task or attach the document.
- [ ] No
---

### User Stories

- **As a** [user type],
**I want** [functionality],
**so that** [benefit].

---

### Design

- **Figma**: [Insert URL]
- **Design Docs**: [Insert URL]

---

### Dependencies

-

---

### Additional Notes

-

---

### Related Issues

-

Contributor guide

No contributing guide indexed for this repository

Research direction

No file, test, or entry point is named. Start by resolving the open questions about group and field error states and recording the agreed visual design; the issue currently does not define implementation locations or a concrete completion criterion.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.