open-telemetry / open-telemetry/opentelemetry-ruby
Continue gem inheritance
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 606
- Forks
- 301
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 42
Description
Recently we started inheriting gems from the root gemfile but currently there is duplicates ie dotenv & simplecov. There is also other gems ie yard which would be more fitting at the root.
We should continue the work to minimise gems in child gem while also ensuring that changing root gemfile has a way to trigger usage of that gem by each child.
Context
This is in already evaled root Gemfile 🤔. https://github.com/open-telemetry/opentelemetry-ruby/blob/ab29f8582ec55ed19276e6b4289fb40683541b58/Gemfile#L9
Originally posted by @simi in https://github.com/open-telemetry/opentelemetry-ruby/pull/2342#discussion_r3961476639
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 with the evaluated root Gemfile at the linked line, then inspect the child Gemfiles for duplicate dependencies such as dotenv and simplecov and candidates such as yard. Done means reducing unnecessary child-gem entries while ensuring a root Gemfile change makes each child use the dependency as intended.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100