Skip to content
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

Add Faker::Gender.short_type #2400

Closed
wants to merge 2 commits into from

Conversation

alessandrapereyra
Copy link

No-Story

Description:

While building a database seeds generator, I noticed there wasn't a non-binary counterpoint of the existing Faker::Gender.short_binary_type for gender markers.

This PR introduces that option using the most common values (f, m, x) and should be able to fulfill similar use cases as the ones described in the original PR.

Let me know if there's anything missing! I reviewed the Contributing guidelines and I think I followed them but let me know if I forgot something 🙏 .

Have a great day!

Copy link

@mattalat mattalat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great!

lib/faker/default/gender.rb Outdated Show resolved Hide resolved
Co-authored-by: matt <17059882+mattalat@users.noreply.github.com>
@stefannibrasil
Copy link
Contributor

Hey there. In an effort to lighten our load as maintainers and be able to serve you better in the future, the faker-ruby team is working on cleaning out the cobwebs in this repo by pruning the backlog. As there are few of us, there are a lot of items that will simply never earn our attention in a reasonable time frame, and rather than giving you an empty promise, we think it makes more sense to focus on more recent issues. That means, unfortunately, that we must close this PR.

Don't take this the wrong way: our aim is not to diminish the effort people have made or dismiss problems that have been raised.

If you feel that we should reopen this PR, please do the following first:

  • rebase with master to fix any conflicts
  • verify this contribution is still relevant (i.e. hasn't been implemented/solved yet)
  • run tests again

Then please let us know so that we can re-prioritize it. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants