Eric Cheng

> OK. > > `strategy: 'fail' | 'return-any' = 'fail'` > > Or `fail-if-unavailable`? Or `throw-if-unavailable`? What about just `throw`?

> This looks ridiculously easy :thinking: _sus_? May or may not have been copy-pasted from GitHub documentation😂

Yes, I think it would be best if we applied the rule on all arrays above a certain length.

> IDK, a test doesn't seem the right thing for me. Since these modules only return a random element from the locale definition. By adding a "test" that `meter` has...

> > These proposed added tests are only to test the off-chance that the definitions were somehow changed and the `name` and `symbol` properties no longer match up with each...

> The suggested solution you provided sounds reasonable to me. Other locales could gain value from this as well. > > In my opinion, we should call the property in...

> > IDK, `crypto()` could fit into the `finance` module and `hashAlorythm()` in the `hacker` module. I don't see the need for a new module. > > That is exactly...

> Currently I dont see a usecase for any of these. What are the user going to do with them? Just because we can generate certain data doesnt mean we...

> I also like the idea, but currently I'm not sure where to put it. On one hand I would like to have all numbers behave like this, on the...

> Should I create a PR for it? Sure, if you're up for it. I'll assign you to this issue if you want to create a PR. Edit: Nvm, just...