Currently, the instructions for these exercises want users to install rspec from the Gemfile using bundle install and then from there, run tests using bundle exec rspec path_to/file_spec.rb. This works fine up until users start the debugging content, where the user cannot access their global install of pry-byebug while running commands prefixed with bundle exec -- leading to require bugs that learners at this stage have a difficult time figuring out. Here's an example from the discord server today, but it has happened multiple times since the debugging exercises were introduced.
I think there are two good ways to approach fixing the problem:
- Go ahead and have the users globally install RSpec -- this is done later down the line anyway -- and then forgo the use of
bundle exec entirely.
- Place
pry-byebug in the Gemfile. It will then be installed in the users' local repo when they initially run bundle install, which will eliminate require errors when using bundle exec.
Would be glad to submit a PR for whichever method is preferable. Also definitely open to other ideas if there are other ways to make this work more smoothly.
Currently, the instructions for these exercises want users to install rspec from the Gemfile using
bundle installand then from there, run tests usingbundle exec rspec path_to/file_spec.rb. This works fine up until users start the debugging content, where the user cannot access their global install ofpry-byebugwhile running commands prefixed withbundle exec-- leading torequirebugs that learners at this stage have a difficult time figuring out. Here's an example from the discord server today, but it has happened multiple times since the debugging exercises were introduced.I think there are two good ways to approach fixing the problem:
bundle execentirely.pry-byebugin the Gemfile. It will then be installed in the users' local repo when they initially runbundle install, which will eliminaterequireerrors when usingbundle exec.Would be glad to submit a PR for whichever method is preferable. Also definitely open to other ideas if there are other ways to make this work more smoothly.