-
-
Notifications
You must be signed in to change notification settings - Fork 943
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
refactor(date)!: stricter error handling of between #2719
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## next #2719 +/- ##
=========================================
Coverage 99.93% 99.94%
=========================================
Files 2960 2958 -2
Lines 211338 213714 +2376
Branches 594 602 +8
=========================================
+ Hits 211203 213592 +2389
+ Misses 135 118 -17
- Partials 0 4 +4
|
Co-authored-by: ST-DDT <ST-DDT@gmx.de>
Co-authored-by: ST-DDT <ST-DDT@gmx.de>
I'm in contact with the codecov team regarding the increased error rate. |
I guess this should revert back to using the new improved "toDate" now that has been merged? |
Yes, please. |
✅ Deploy Preview for fakerjs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
fix #2711
Note i didn't change
toDate
function, as the new version ofbetween
doesn't need it any more. That could be done in a seperate PR if required.Some errors are only possible to trigger in JS (e.g. omitting params) but invalid string dates can be passed in TS too.