ruby / ruby/irb

Configs that haven't been covered by tests

Open
#630 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

rubyconf-hackdays
Dominant language
Ruby
Stars
478
Forks
158
Avg merge
1d 12h
Merged PRs (30d)
12

Description

These are the configs (IRB.conf[config_name]) referenced in Context#initialize but not covered by any test cases (probably `test_context.rb):

  • :AP_NAME
  • :LOAD_MODULES
  • :USE_TRACER - This could be broken with ruby/tracer version. May need to drop it directly
  • :USE_LOADER
  • :IGNORE_EOF
  • :BACK_TRACE_LIMIT
  • :IRB_NAME
  • :EXTRA_DOC_DIRS

Contributor guide

Open the contributing guide

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.

Research direction

Start with Context#initialize and the existing tests in test_context.rb, then trace each listed IRB.conf config to understand its expected behavior. Add coverage for AP_NAME, LOAD_MODULES, USE_TRACER, USE_LOADER, IGNORE_EOF, BACK_TRACE_LIMIT, IRB_NAME, and EXTRA_DOC_DIRS, with tests demonstrating the intended behavior for each.

Written by the indexing model from the issue text.

Assessment

Tech stack
ruby
Domain
cli, testing
Issue type
Refactor
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.