Validation errors not showing up for type day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- react, typescript
- Domain
- frontend
Research direction
Start with the linked CodeSandbox reproduction and reproduce the missing day-component error during typing and submission. Trace the day component's validation error rendering and class application, comparing it with the textfield behavior. Done means the custom error is visible in both flows without the workaround.
Written by the indexing model from the issue text.
Description
I have a form with two components, one of type day, with day, month and year required, and one of type textfield, required. Both have a custom error message.
Both while typing and on submission, errors are not shown for the day component. I tried calling the submit function and I noticed the error is actually thrown. It seems like the library is not adding the correct class to the element in order for the error to be shown.
To Reproduce
Steps to reproduce the behavior:
- Go to repro: https://codesandbox.io/p/sandbox/modest-worker-mtztn2
- Click on "verify"
- See that error on day is not shown
- Click on "vertify with workaround"
- See that error on day is now shown thanks to the ugly workaround I implemented
Expected behavior
Errors on day component should be shown both while typing and on submit
Screenshots
Without workaround:
With workaround:
Desktop (please complete the following information):
- OS: Tested on Windows 10 and macOS 14.5
- Browser chromium based
- Version 127.0.6533.73
Additional context
The version of the libs in the repro are the exact ones I use in my project
- Dominant language
- TypeScript
- Stars
- 371
- Forks
- 309
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from formio/react
-
Difficulty 3/5 1-2 days Newbie friendliness 64/100
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
onChange `modified` property remains false when file component is updatedMay be free again @ZenMasterJacob20011 claimed this 295 days ago, and no pull request is open. Open
-
FormBuilder onChange callback not triggered when options prop is providedMay be free again @Victoriya25 claimed this 337 days ago, and no pull request is open. Open
-
FormBuilder with OnChange broke textareaMay be free again @lane-formio claimed this 309 days ago, and no pull request is open. Open
Similar issues
-
`@angular/[email protected]` depends on vulnerable Vite 7.3.7 - GHSA-p4f5-76q4-ffq7 (Critical RCE)Openarea: @angular/build
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
angular/angular-cli#34764 ·
Maintainers usually reply within 1 day
-
status/need-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
google-gemini/gemini-cli#30384 · 1 comment ·
Maintainers usually reply within 1 day
-
P2
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
bug ready-for-human
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
LucasSantana-Dev/Lucky#3150 ·
Maintainers usually reply within 1 day
-
enhancement good first issue priority: low size: XS
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day