refactor(person): refine usage of PersonEntryDefinitions

[ST-DDT]

Fixes #3058

• Clean up generic prefixes #3058

Next steps: #3266

• refactor(locale): filter and cleanup PersonEntryDefintions data #3266

Meeting-Notes: 2024-11-07

---

This PR tries to lay the foundation of what is considered generic and what is specifically sexed:

• Generic: Values that can be attributed to/used by either of male or female persons. (e.g. Dr.)
• Female/Male: Values that can be attributed to specifically female/male (e.g. Mrs./Mr.)

It also changes the way how definitions are selected:

• If generic is requested: Then only values that are specifically generic are returned, unless there are no such values.
• If female/male is requested: Then the method will mostly (80%) return female/male values with some (20%) generic values sprinkled in. Since generic can explicitly be both, the generic elements don't cause any issues.

Please check whether the definitions/jsdoc are clear regarding their intentions and if you consider this definition to be correct.
We will clean up the locale data in separate PRs as this might affect lots of files/locales.

[netlify]

✅ Deploy Preview for fakerjs ready!

Name	Link
🔨 Latest commit	9b28f06
🔍 Latest deploy log	https://app.netlify.com/sites/fakerjs/deploys/673fb3938a5f430008747901
😎 Deploy Preview	https://deploy-preview-3259.fakerjs.dev
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[codecov]

Codecov Report

Attention: Patch coverage is 94.11765% with 2 lines in your changes missing coverage. Please review.

Project coverage is 99.95%. Comparing base (56acea3) to head (9b28f06).

Files with missing lines	Patch %	Lines
src/modules/person/index.ts	94.11%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             next    #3259      +/-   ##
==========================================
- Coverage   99.97%   99.95%   -0.02%     
==========================================
  Files        2806     2806              
  Lines      217156   217175      +19     
  Branches      982      978       -4     
==========================================
- Hits       217092   217086       -6     
- Misses         64       89      +25     

Files with missing lines	Coverage Δ
src/definitions/person.ts	100.00% <ø> (ø)
src/modules/person/index.ts	96.66% <94.11%> (-0.28%)	⬇️

... and 2 files with indirect coverage changes

---- 🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests
• JS Bundle Analysis - Avoid shipping oversized bundles

[matthewmayer]

I understand wanting to keep this PR small but I think it's difficult to decide if this is the right approach without reviewing what locale files will need to be updated too.

To clarify with this approach would we require the "generic", "female" and "male" options never have any items in common?

[ST-DDT]

Team Decision

We will change the sexType method to return all SexType values.
A parameter includeGeneric: boolean = false can be used to control the inclusion of generic in the results.
We will check in v10 whether we want to change the default for includeGeneric based on code usage?

ST-DDT: Will create a stacked PR for the locale changes.

• Things in both female and male -> generic
• Things in generic -> remove from female and male
• Without manual changes
• The stacked PR might be later split in smaller chunks to help with reviewability

[ST-DDT]

ST-DDT: Will create a stacked PR for the locale changes.

[...]

• Without manual changes
• The stacked PR might be later split in smaller chunks to help with reviewability

@xDivisionByZerox Currently, the person files aren't sorted, so this by itself causes a massive diff.
Should we sort them first? Would you like to create a PR for that or should I?

(Maybe start with only sorting first, because the cleanup PR will use the list for filtering: See #3266 (comment))

[xDivisionByZerox]

@xDivisionByZerox Currently, the person files aren't sorted, so this by itself causes a massive diff.
Should we sort them first? Would you like to create a PR for that or should I?

Please go ahead. I'm not available during the weekend, sadly.

[ST-DDT]

Done: #3269

• refactor(locale): sort person data #3269