Deprecate multi-irb feature
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Ruby
- Stars
- 478
- Forks
- 158
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 12
Description
Plan
- Print deprecation warnings on these commands:
irb,jobs,fg, andkillin the next minor release - Completely remove those commands in
v2.0.0
Reasons
- It's concept highly overlaps with workspace commands like
chws,pushws...etc. - It spawns a new thread for every new new session, which conflicts with the upcoming irb-debug integration
- But most importantly, we can't find any practical use for this feature and the cost of maintaining its compatibility with other features is high
- For example, it will require the solution of #650 to support multi-thread irb sessions too
Feedback wanted
If you use the multi-irb feature and don't want to see it deprecated from IRB, please leave a comment below to explain your use case of it. It will help us assess this plan.
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 locating the implementations and command handling for irb, jobs, fg, and kill, then inspect how IRB versions and deprecations are managed. Done means those commands warn in the next minor release and are removed in v2.0.0, with the relevant tests updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- cli
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100