✨ Introduce new fc.noShrink arbitrary
#5047
Conversation
While `noShrink` used to be a thing directly provided on the arbitrary since version 0.0.9, we want to extract it as an independant arbitrary. Such extraction would allow us to reduce the API surface of the arbitraries to a smaller subset of methods. Aim being to reduce as much of possible the API users will have to deal with from the arbitrary itself.
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 6147b58:
|
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 774d49a:
|
|
👋 A preview of the new documentation is available at: http://6661108bb4321a29b807da46--dubzzz-fast-check.netlify.app |
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit c9c2d72:
|
|
👋 A preview of the new documentation is available at: http://66611302063eb0286907b7f5--dubzzz-fast-check.netlify.app |
Description
While
noShrinkused to be a thing directly provided on the arbitrary since version 0.0.9, we want to extract it as an independant arbitrary.Such extraction would allow us to reduce the API surface of the arbitraries to a smaller subset of methods. Aim being to reduce as much of possible the API users will have to deal with from the arbitrary itself.
Related to the PR #4162
Checklist — Don't delete this checklist and make sure you do the following before opening the PR
yarn bumpand flag the impacts properlyAdvanced
Arbitrary.prototype.noShrink