Generating your client validation rules
summary
Enterprise forms cause CPU spikes so the team rewrites the front end with React and needs client-side validation that matches a backend XML rule set. The pipeline parses the giant XML config, runs SharpTJS generator, emits a plain static JS rule file with simple if comparisons, ships it as static content, and runs validations locally with a server fallback. Result: far fewer server calls, instant feedback, easy debugging, and regenerated rules per customer config.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:46eVision Industry
- 1:12Performance related Problems Challenges
- 1:37Rewrite of the UI stack
- 2:03Handle validations
- 2:31Options for client Ask the server
- 3:23Generation
- 3:43Example
- 3:59Benefits
- 5:28Disclaimer
related talks
21mForm Validation Done Right
28mBuilding validated forms with great UX in React
34mDesigning form validation the right way
25mRe-Form the future. Rethinking Form Validations in React
38mFull Stack Form Validation with React Server Actions
26mThe Art of Building Modern Dynamic Forms
16mBuilding Server Driven UI
27mEnhancing Forms with React Server Components and React 19