Accept readonly versions of the contraints passed to the arbitraries #5007
Labels
💡 Idea to investigate
Non straightforward features that seems great but need to be assessed and designed carefully.
💥 Targeting unplanned major
Breaking change for an upcoming major version, but not blocker for any major.
🚀 Feature Request
Motivation
There is no need for our arbitraries to require non-readonly options. They should be ok with receiving readonly versions of their constraints.
Needed for next major! Probably acceptable for current minor too!
More details on frozen, sealed... at https://www.codecademy.com/resources/docs/javascript/objects/isFrozen.
The text was updated successfully, but these errors were encountered: