-
-
Notifications
You must be signed in to change notification settings - Fork 1k
test: use validator@13.15.0 with isULID, isISO31661Numeric, isISO15924 #3482
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test: use validator@13.15.0 with isULID, isISO31661Numeric, isISO15924 #3482
Conversation
✅ Deploy Preview for fakerjs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## next #3482 +/- ##
=======================================
Coverage 99.97% 99.97%
=======================================
Files 2838 2838
Lines 218606 218606
Branches 949 949
=======================================
Hits 218553 218553
Misses 53 53 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are the checks prior to the validation function still useful? Since validator works with regex under the hood most of the time, I'm not seeing how having two regex is useful for us.
I don't see much point in removing them |
By upgrading @types/validator to @13.15.0 we can take advantage of the new functions isULID, isISO31661Numeric and isISO15924 from validator to improve and simplify tests.