You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
✨ Add support for string-unit on object/anything arbitrary (#5366)
**Description**
<!-- Please provide a short description and potentially linked issues
justifying the need for this PR -->
The `unit` field has been added pretty recently to `string` in order to
offer ways for our users to control in a more granular way what kind of
"character" they would like to be generated for their strings. In order
not to mix "character" with the characters in JavaScript and to allow
any feasible grapheme or combination of code-points to be a valid
"character" we refer to them as "unit".
This PR adds supports for units of strings from object builders.
<!-- * Your PR is fixing a bug or regression? Check for existing issues
related to this bug and link them -->
<!-- * Your PR is adding a new feature? Make sure there is a related
issue or discussion attached to it -->
<!-- You can provide any additional context to help into understanding
what's this PR is attempting to solve: reproduction of a bug, code
snippets... -->
**Checklist** — _Don't delete this checklist and make sure you do the
following before opening the PR_
- [x] The name of my PR follows [gitmoji](https://gitmoji.dev/)
specification
- [x] My PR references one of several related issues (if any)
- [x] New features or breaking changes must come with an associated
Issue or Discussion
- [x] My PR does not add any new dependency without an associated Issue
or Discussion
- [x] My PR includes bumps details, please run `yarn bump` and flag the
impacts properly
- [x] My PR adds relevant tests and they would have failed without my PR
(when applicable)
<!-- More about contributing at
https://github.com/dubzzz/fast-check/blob/main/CONTRIBUTING.md -->
**Advanced**
<!-- How to fill the advanced section is detailed below! -->
- [x] Category: ✨ Introduce new features
- [x] Impacts: New flags for finer control on some arbitraries
<!-- [Category] Please use one of the categories below, it will help us
into better understanding the urgency of the PR -->
<!-- * ✨ Introduce new features -->
<!-- * 📝 Add or update documentation -->
<!-- * ✅ Add or update tests -->
<!-- * 🐛 Fix a bug -->
<!-- * 🏷️ Add or update types -->
<!-- * ⚡️ Improve performance -->
<!-- * _Other(s):_ ... -->
<!-- [Impacts] Please provide a comma separated list of the potential
impacts that might be introduced by this change -->
<!-- * Generated values: Can your change impact any of the existing
generators in terms of generated values, if so which ones? when? -->
<!-- * Shrink values: Can your change impact any of the existing
generators in terms of shrink values, if so which ones? when? -->
<!-- * Performance: Can it require some typings changes on user side?
Please give more details -->
<!-- * Typings: Is there a potential performance impact? In which cases?
-->
-`withUnicodeString?` — default: `false` — _change the default for `key` and `values` so that they produce unicode strings with non-ascii characters_
186
+
-`withUnicodeString?` — default: `false` — _change the default for `key` and `values` so that they produce unicode strings with non-ascii characters — shadowed by `stringUnit`_
187
+
-`stringUnit?` — default: `undefined` — _customize the set of characters being used by the `string` arbitrary_
187
188
-`values?` — default: _booleans, numbers, strings, null and undefined_ — _array of arbitraries producing the root* values - *non-object ones_
188
189
189
190
**Usages:**
@@ -276,7 +277,7 @@ Generate any kind of entities.
0 commit comments