Bundler Workspace?
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 4k
- Forks
- 1.9k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 81
Description
Describe the problem as clearly as you can
In both yarn and cargo, each has the concept of workspaces. Or a way to build multiple packages with shared dependencies. In poetry a similar discussion is taking place - https://github.com/python-poetry/poetry/issues/936.
In ruby, perhaps we could have a file structure like:
- workspace.Gemfile # includes libraries like
standardandrspec - gems/
- gem_a/
- Gemfile # includes gem_a.gemspec
- gem_b/
- Gemfile # includes gem_b.gemspec
- gem_a/
How can we bring these ideas to ruby? If there's an ongoing effort I'm happy to contribute, my company @neonlaw is also open to sponsoring development for this. Thanks!
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
The issue names no files or tests; start by reviewing Bundler's current project and dependency model, then compare it with the yarn, cargo, and linked Poetry workspace discussions. Define the workspace file structure and shared-dependency behavior before implementation; done requires an agreed design and support for multiple gems.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100