Improve core/stdlib signature coverage
Open
Nobody has claimed this yet.
good first issue
- Dominant language
- Ruby
- Stars
- 2.2k
- Forks
- 256
- Avg merge
- 6d 17h
- Merged PRs (30d)
- 37
Description
We provide the signatures of a very limited number of standard library classes. We will really appreciate if you write the signature of other classes.
(Note that we are currently working for standard library signatures.)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the existing core/stdlib signature coverage and how standard library classes are represented. The issue does not identify target classes, files beyond core/stdlib, or tests, so confirm the intended scope before adding signatures; done means covering the agreed additional standard library classes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100