Validate Forms Progressively from Blur to Submit
Validate on blur, then on change after first error, then on submit so the user gets feedback without aggressive red fields on first focus.
Task
Add const schema = z.object({ email: z.string().email() }); validateOnBlur(form, schema); so the interface remains usable and accessible under the edge cases that manual testing skips.
When to use this
A screen reader user reports the page is unusable because const schema = z.object({ email: z.string().email() }); validateOnBlur(form, schema); was never implemented, flagged in a support ticket.
Prerequisites
- A frontend component or page in the codebase
- A build with the relevant framework configured
Steps
1. Configure const schema = z.object({ email: z.string().email() }); validateOnBlur(form, schema); in the project configuration file with the recommended defaults.
const schema = z.object({ email: z.string().email() }); validateOnBlur(form, schema);
Expected output: The configuration is accepted and const schema = z.object({ email: z.string().email() }); validateOnBlur(form, schema); runs without errors on the first invocation.
2. Run the check locally to verify const schema = z.object({ email: z.string().email() }); validateOnBlur(form, schema); produces the expected result before pushing.
pnpm test
Expected output: Local run matches CI behavior; no surprises after push.
3. Add the gate to the CI pipeline so const schema = z.object({ email: z.string().email() }); validateOnBlur(form, schema); blocks merge on failure.
- name: Run add form validation progressive
run: pnpm test
Expected output: Pull requests with failing const schema = z.object({ email: z.string().email() }); validateOnBlur(form, schema); are blocked from merging.
Troubleshooting
Problem
The check passes locally but fails in CI
Solution
Pin dependency versions and the runtime to match CI exactly; reproduce with the same Docker image or act.
Problem
Configuration is rejected with a schema error
Solution
Check the tool version matches the config schema; older versions may not support newer fields.
Limitations
- The gate only runs on events that trigger the workflow; locally pushed commits bypass it.
- Configuration drift is possible if someone edits settings outside version control.
Handle the edge case
Start by measuring the problem. Validate on blur, then on change after first error, then on submit so the user gets feedback without aggressive red fields on first focus. The most common mistake is adding the gate without first confirming it catches the issue you care about. Run const schema = z.object({ email: z.string().email() }); validateOnBlur(form, schema); against the current codebase and inspect the output before wiring it into CI.
const schema = z.object({ email: z.string().email() }); validateOnBlur(form, schema);Test with real tools
Once the gate is in place, make failures actionable. A failing const schema = z.object({ email: z.string().email() }); validateOnBlur(form, schema); should point to the exact file and line, not a generic error. Pin the tool version in the lockfile so a upstream release does not silently change behavior. Review the gate output in every pull request just like a test result.