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 Rake task for creating an autogenerated rbi #1936

Closed
wants to merge 5 commits into from

Conversation

connorshea
Copy link
Member

Issue#

#1854

Description:

This is a WIP PR. It also includes commits from #1853 and #1935.

I'm using the same system as I did in December (described in this gist) and it still works perfectly fine, so I'm comfortable recommending it now.

The Sord generator isn't perfect, so this requires a few workarounds to fix some invalid code within the generated RBI, that's all handled in the Sord Rake task.

I'll work on getting a new Sord release out so we can add it as a development dependency in the gemspec rather than a dependency in the Gemfile itself.

If you'd prefer not to have to maintain this as part of the gem, I'm fine with that and I can add it to sorbet-typed instead. This is mostly an experiment to see if autogenerated types like this are viable.

See the Sorbet docs on RBIs within gems.

@connorshea connorshea marked this pull request as ready for review February 16, 2020 04:13
connorshea added a commit to connorshea/sorbet-typed that referenced this pull request May 31, 2020
Built with Sord, from this PR: faker-ruby/faker#1936
elliottt pushed a commit to sorbet/sorbet-typed that referenced this pull request Jun 2, 2020
The constant doesn't get output in the RBI, which means that its
usage as the default parameter value is invalid.
@thdaraujo
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
  • 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!

@thdaraujo thdaraujo closed this Aug 5, 2022
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.

2 participants