Skip to content
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

Accept readonly versions of the contraints passed to the arbitraries #5007

Open
dubzzz opened this issue May 21, 2024 · 0 comments
Open

Accept readonly versions of the contraints passed to the arbitraries #5007

dubzzz opened this issue May 21, 2024 · 0 comments
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.

Comments

@dubzzz
Copy link
Owner

dubzzz commented May 21, 2024

🚀 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.

@dubzzz dubzzz added 💥 Targeting unplanned major Breaking change for an upcoming major version, but not blocker for any major. 🚀 Feature Request ✔️ Feature Accepted labels May 21, 2024
@dubzzz dubzzz added 💡 Idea 💡 Idea to investigate Non straightforward features that seems great but need to be assessed and designed carefully. and removed 💥 Targeting unplanned major Breaking change for an upcoming major version, but not blocker for any major. 🚀 Feature Request ✔️ Feature Accepted labels May 21, 2024
@dubzzz dubzzz added 💥 Targeting unplanned major Breaking change for an upcoming major version, but not blocker for any major. and removed 💡 Idea labels Mar 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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.
Projects
None yet
Development

No branches or pull requests

1 participant