Identify and skip `development` dependencies

Open
#1,817 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
ruby
Domain
tooling

Research direction

Start by tracing the rbs collection entry point and the logic that looks for sig/ files, then inspect how Gemfile groups and gemspec dependencies are currently identified. Done means both paths recognize development dependencies and skip them when appropriate.

Written by the indexing model from the issue text.

Description

There are practices to differentiate “development apps” (e.g., use Rake to automate, use RBS to test) and “runtime libraries” (e.g., Rake plugin, RBS processor) in Gemfiles and .gemspecs.

# Gemfile
group :development do
  gem 'rake', …
  gem 'rbs', …
end

# *.gemspec
…
  add_development_dependency 'rake', …
  add_development_dependency 'rbs', …
…

RBS – both rbs collection as well as when looking for sig/s in general – should learn to identify those patterns.

Originally posted by @ParadoxV5 in https://github.com/soutaro/rbs-inline/issues/11#issuecomment-2101120845

Dominant language
Ruby
Stars
2.2k
Forks
263
Avg merge
1d 20h
Merged PRs (30d)
64

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ruby/rbs

All issues in ruby/rbs

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.