Pronouns

[matthewmayer]

Clear and concise description of the problem

Many online services now allow users to specify their pronouns e.g.
https://slack.com/help/articles/1500011115781-Manage-pronoun-and-name-pronunciation-display-for-member-profiles
https://www.linkedin.com/business/talent/blog/talent-acquisition/pronouns-you-might-see-on-candidate-profiles
https://support.zoom.us/hc/en-us/articles/4402698027533-Adding-and-sharing-your-pronouns

For generating realistic fake profiles it would be useful to have a faker method to generate pronouns

Suggested solution

Add faker.name.pronouns()

Although there are many neo-pronouns, a simple implementation could just be a random selection from
he/him
she/her
they/them
in English, and suitable localizations for other languages.

Alternative

You could just do this manually

Additional context

No response

[ST-DDT]

@matthewmayer Is this specifically for bios or just a way to generate pronouns?

[matthewmayer]

Just pronouns. It's quite common on social media profiles, to have a specific field for pronouns. Instagram and LinkedIn have them for example.

[ST-DDT]

There are different variants of pronouns he vs him (er vs ihm) and I'm sure there are different names for them in every language.
Which ones do we support or how do we support switching between them?

[matthewmayer]

the common way in English to write this seems to be just subject pronoun / object pronoun.

ie this would just be effectively:

faker.helpers.arrayElement(["he/him","she/her","they/them"])

[github-actions]

Thank you for your feature proposal.

We marked it as "waiting for user interest" for now to gather some feedback from our community:

• If you would like to see this feature be implemented, please react to the description with an up-vote (:+1:).
• If you have a suggestion or want to point out some special cases that need to be considered, please leave a comment, so we are aware about them.

We would also like to hear about other community members' use cases for the feature to give us a better understanding of their potential implicit or explicit requirements.

We will start the implementation based on:

• the number of votes (:+1:) and comments
• the relevance for the ecosystem
• availability of alternatives and workarounds
• and the complexity of the requested feature

We do this because:

• There are plenty of languages/countries out there and we would like to ensure that every method can cover all or almost all of them.
• Every feature we add to faker has "costs" associated to it:
  • initial costs: design, implementation, reviews, documentation
  • running costs: awareness of the feature itself, more complex module structure, increased bundle size, more work during refactors

---

View more issues which are waiting for user interest

[LauraWebdev]

With the increase of profiles having a dedicated pronouns field, this would definitely be something worth to develop. I've had to fallback with a random selection for mocking my API for now.