-
-
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
feat(name): extract sex generator from gender to sex #1168
Conversation
Co-authored-by: Piotr Kuczynski <[email protected]>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Codecov Report
@@ Coverage Diff @@
## main #1168 +/- ##
=======================================
Coverage 99.62% 99.62%
=======================================
Files 2158 2159 +1
Lines 240193 240217 +24
Branches 1003 1005 +2
=======================================
+ Hits 239294 239325 +31
+ Misses 878 871 -7
Partials 21 21
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a breaking change as binary_gender
could be used in faker.faker('{{binary_gender}}')
without that we know it or users know that it had changed
I mark this as blocked for now and would like to first discuss if this PR is needed anyway
If we are killing In my opinion So yes, technically it could be a breaking change, but at the same time locale formats are not officially published, so I have doubts if anybody would hook up to the internals so deep to find it. And if he did, it's kind of not our fault... @ST-DDT @xDivisionByZerox wdyt? |
# Conflicts: # test/__snapshots__/name.spec.ts.snap # test/name.spec.ts
I believe I applied all of the feedback. Is there anything else I should do about it? |
Ping @ST-DDT, you need to approve to stale your requested changes |
Fixes #353
Fixes #776
name.gender(true)
, which generated binary gender, what we would consider now assex
binary_gender
tosex
sex
non-binary