-
-
Notifications
You must be signed in to change notification settings - Fork 186
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
💥 Include invalid dates by default #5589
Conversation
**💥 Breaking change** In v3, `fc.date` was not producing "Invalid Date" values by default. One has to specify `noInvalidDate: false` to get some. With this PR we now default the flag to false when not specified: in other words, the new default will be to produce invalid dates except asked explicitly not to. After that change, if you want not to produce "Invalid Date", you'll have to use: ```js // in v3, it was only producing valid dates fc.date() // equivalent in v4 fc.date({noInvalidDate: true}) //--- // in v3, including invalid dates required users to pass an extra constraint to the arbitrary fc.date({noInvalidDate: false}) // equivalent in v4 fc.date() ``` You can also prepare yourself to v4 by already toggling: `noInvalidDate: false` on your `fc.date`.
🦋 Changeset detectedLatest commit: 4001a66 The changes in this PR will be included in the next version bump. This PR includes changesets to release 5 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Open in Stackblitz • @fast-check/examples @fast-check/ava
@fast-check/expect-type
@fast-check/jest
fast-check
@fast-check/packaged
@fast-check/poisoning
@fast-check/vitest
@fast-check/worker
commit: |
👋 A preview of the new documentation is available at: http://677f896b99c26b0d7c358ef9--dubzzz-fast-check.netlify.app |
👋 A preview of the new documentation is available at: http://677f8b1e1ad8e3000c5ef85b--dubzzz-fast-check.netlify.app |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #5589 +/- ##
=======================================
Coverage 94.90% 94.90%
=======================================
Files 235 235
Lines 10024 10024
Branches 2823 2823
=======================================
Hits 9513 9513
Misses 511 511
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Description
In v3,
fc.date
was not producing "Invalid Date" values by default. One has to specifynoInvalidDate: false
to get some. With this PR we now default the flag to false when not specified: in other words, the new default will be to produce invalid dates except asked explicitly not to.After that change, if you want not to produce "Invalid Date", you'll have to use:
You can also prepare yourself to v4 by already toggling:
noInvalidDate: false
on yourfc.date
.Checklist — Don't delete this checklist and make sure you do the following before opening the PR
yarn bump
and flag the impacts properlyAdvanced
💥 Breaking change: Change defaults on date