Matt Mayer
Matt Mayer
Would it be better just to explicitly test each method in turn? Its repetitive but maybe easier to understand. Most other simple modules, even ones which are just helpers.arrayElement wrappers...
> Would it be better just to explicitly test each method in turn? Its repetitive but maybe easier to understand. Most other simple modules, even ones which are just helpers.arrayElement...
Or a date method 😀
Note this should be cleaned up in other locales e.g. https://github.com/faker-js/faker/blob/next/src/locales/en/person/prefix.ts where generic is just the union of male and female.
Currently `en` has: ``` export default { generic: ['Dr.', 'Miss', 'Mr.', 'Mrs.', 'Ms.'], female: ['Mrs.', 'Ms.', 'Miss', 'Dr.'], male: ['Mr.', 'Dr.'], }; ``` which should be ``` export default {...
Strong support. I find the dependency notifications very spammy And given faker only has devDependencies I don't think there is such an urgency to always be on the bleeding edge...
This definitely seems confusing to navigate. There is no way to know what signature you need without clicking on all of them. Having a single table with all the parameters...
I'm not really sure showing multiple signatures is necessary. Given most methods have very simple signatures (just passing an options object). Showing a good set of examples is probably easier...