Illia Pantsyr
Illia Pantsyr
I thought it would be better to use `locale.yml` to maintain consistency (I mean that all fakers have a corresponding `.yml` ).
I can't understand why in most repeated test runs with over 1.000 iterations, there is 1 `Locale.baseLocale()` fall
`LocaleFakerTest.baseLocale()`
``` Croatian Chechen (Cyrillic, Russia) English (Malta) Punjabi (Gurmukhi, India) Albanian (Latin, Albania) Northern Sami Inari Sami English (Macao SAR China) Koyraboro Senni (Latin, Mali) Cebuano (Philippines) French (Belgium) Sangu...
Result of `LocaleFaker.baseLocale()`: ``` sr_ME ms_MY doi_IN en_VC el_GR mg_MG rm_CH seh_MZ nl_BE mzn_IR ne_NP ar_JO ``` Result of `LocaleFaker.displayName()`: ``` Swedish English (Antigua & Barbuda) Chakma (Bangladesh) Danish (Denmark)...
@snuyanzin If it's better to have one, then how to implement generation of random locales. As I see, `LocalePicker` is a service, and isn't accessible via `Faker` instance, the solution...
Looking at such significant changes in the project, I think it is better to close this pull request and add this provider in the new one
@bodiam I could take up this task. But, first, I wanted to know in a few words how it should look like. For example, in the `.yml` files add lists...
Current state of `PhoneNumberValidityFinderTest.testAllPhoneNumbers` test: ``` sk_SK=65 lv_LV=72 fr_CH=73 en_MS=74 pt_PT=76 tr_TR=84 zh_CN=89 hu_HU=94 by_BY=95 ar_AR=97 es_AR=98 sv_SV=100 ```
@bodiam `sv_SV` is this the correct one? Because I cannot find any information about it. Maybe it's `sv_SE`?