Having 15-year experience in web development, I have tried my hands at dozens of validation libraries but didn’t manage to find the one to handle all my tasks. 5 years ago we decided to create a validator which will better than any other. Now LIVR supports a dozen of programming languages and it is battle tested in hudrends of projects. I will talk about the ideas behind, about architecture, use cases, pros and cons. Will show real examples.
2. Viktor Turskyi
● CEO and principal architect at
WebbyLab
● Open source developer
● More than 15 years of experience
● Delivered more than 60 projects of
different scale
● Did projects for 5 companies from
Fortune 500 list
8. Issue 1: Some validators pass through fields
which have no validation rules described
Issue 2: Some validators fails on the first error
9. Issue 3: Some validators use procedural rules
Issue 4: Some validators describe validation as a
code
10. Issue 5: Some validators have non standardized
error messages.
Like “Field name is required”
Issue 6: Some validators have numeric error
codes
11. Issue 7: Some validators do not support
hierarchical data structures
Issue 8: Some validators are limited by built-in
rules
12. Issue 9: Some validators have to broad
responsibility. Like working with HTML etc
Issue 10: Some validators do not support
transformation of validation data
34. JS Implementation features
● Zero dependencies
● Passes 100% of spec tests
● Works in NodeJs and in a browser
● Validator itself 1008 B (min+gzip)
● Validator with all rules 2.84KB (min+gzip)
● Extra rules pack - livr-extra-rules (zero deps)