-
-
Notifications
You must be signed in to change notification settings - Fork 919
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
refactor(helpers): introduce allowHuge flag #3256
base: next
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for fakerjs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## next #3256 +/- ##
==========================================
- Coverage 99.96% 99.96% -0.01%
==========================================
Files 2805 2806 +1
Lines 217115 217130 +15
Branches 976 976
==========================================
+ Hits 217049 217051 +2
- Misses 66 79 +13
|
Should this maybe just be a warning rather than an error? |
For now, I opted for an error as there is a strong connection between the error and the call location. A warning just appears in the log and needs extra context for assiciating it with the source. If the others think, this should be a warning or should (not) be there at all. I would like to hear about it as well. |
Second part of #2695
Adds a
allowHuge
flag tofaker.helpers.multiple
. If not set, the number of elements is limited to < 1 Mio.I considered lowering the limit to just 100k as even 1 Mio elements take quite the while to generate.
Once this PR is accepted I'll continue with the string and lorem(?) module.