Validation errors not showing up for type day

Open
#572 2 comments 0 reactions 0 assignees View on GitHub

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

help wanted

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:

  1. Go to repro: https://codesandbox.io/p/sandbox/modest-worker-mtztn2
  2. Click on "verify"
  3. See that error on day is not shown
  4. Click on "vertify with workaround"
  5. 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:
image
With workaround:
image

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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from formio/react

All issues in formio/react

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.