-
-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wiki Outdated? #174
Comments
It depends on how you use it. If you use it with Rails, then you added it to the Gemfile and Rails automatically loads all dependencies on boot, therefore you don't need to manually require it. If you use it elsewhere then you still need to manually require it. |
I've added it to the Gemfile, as I would add any Python dependency to But I am not using Rails, no. |
It was unfair to say that Rails is the only tool that automatically does it. Many frameworks do. In fact, this isn't about any framework. It's just Bundler. In your code, somewhere, there's either a call to a You can test it yourself by creating an empty project and adding 'pry' to the Gemfile. It won't load automatically, unless you require pry manually or call: require 'bundler'
Bundler.require(:default) You can read more about this here. As a side note, requiring any gem is just done once, so even if you execute
I once worked in a team where people had multiple debugging tools and not all of them used |
https://github.com/deivid-rodriguez/pry-byebug/wiki/Using-pry-byebug-inline
I haven't
require
d'pry'
since I started using the plugin.I could obviously fix it myself, I wanted to ask first though. I am not sure if there is any reason to keep the page, other than quick code example
The text was updated successfully, but these errors were encountered: