reload! - undefined method

[scottwater]

Using pry-rails (0.1.2) causes reload! to no longer work in Rails 3.2. with Ruby 1.9.3.

If I remove the pry-rails gem and use irb, it works as expected.

Exact Message:

Loading development environment (Rails 3.2.0)
[1] pry(main)> reload!
NoMethodError: undefined method `reload!' for main:Object

Thanks,
Scott

P.S. I also noticed the app variable is no longer available.

[eagsalazar]

same problem. please document a workaround or add these helpers. Thanks.

[scottwater]

A short term fix is to do this in the console:

self.send(:include, Rails::ConsoleMethods)

I have a pull request coming which does this as well....although it feels a little dirty.

[Tomtomgo]

Is there a way to add this to the 'rails c' startup sequence? Now I'ḿ copy-pasting this everytime...

[scottwater]

@Tomtomgo - Grab the latest version of the gem. The fix has been merged in.

[Tomtomgo]

Nice one.

[joshco]

I'm still seeing a problem : (Win7 mingw, pry 0.9.10)
pry is the only gem installed (no pry-*)
Im running pry -r ./config/environment

[4] pry(main)> reload
NameError: undefined local variable or method reload' for main:Object from (pry):4:inpry'
[5] pry(main)> reload!
NoMethodError: undefined method reload!' for main:Object from (pry):5:inpry'
[6] pry(main)> self.send(:include, Rails::ConsoleMethods)
NameError: uninitialized constant Rails::ConsoleMethods
from (pry):6:in `pry'
[7] pry(main)>

[volkanunsal]

Same problem here....

[lishuaiii]

Same problem

[jessicard]

Same problem on Rails 3.2, Ruby 2.1.1 :(

[rf-]

In addition to the possibility that this is a bug, there are a couple of non-bug reasons this could be happening to you.

First of all, the helpers are only available if you run rails console, not if you use binding.pry within your app. This is following the lead of Rails, which only loads those methods in the console context and not when you run rails server or specs or whatever.

Another potential reason they might not be there is if you've cded or binding.pryed into a context other than the top level. Before Rails 3.2, the app, helper, and reload! methods got mixed into Object, so they would be available regardless of what context you're running code in. Since Rails 3.2, they've been mixed into the top-level context (main) instead, so they're only available in the context that the console initially starts in. We could change that, but it would be different from the stock behavior of Rails.

BTW, I feel like either of those decisions could be revisited if people want the extra convenience in exchange for monkey-patching Object more aggressively. I don't think anyone has ever explicitly asked for those changes, but they would probably reduce confusion, so maybe we should talk about it.

If anyone in this thread is seeing this problem and the reasons above don't apply, please leave some extra details about what you're doing so that we can try to track down what's going on.

[lime]

Thanks @rf-, that clarifies a lot of things! I was pretty confused when rails console gave me the helpers while zeus console and binding.pry did not.

Also, I think the initiative to consider changing this behaviour is great. Maybe it should have its own issue however, so as not to hijack this discussion?

[baweaver]

I'd consider that for another issue. If you're in a Rails app, chances are high that you probably want to have everything loaded in as well.

[umuro]

Reload workaround is as follows:

~/.pryrc

if defined?(Rails) && Rails.env
  if defined?(Rails::ConsoleMethods)
    include Rails::ConsoleMethods
  else
    def reload!(print=true)
      puts "Reloading..." if print
      ActionDispatch::Reloader.cleanup!
      ActionDispatch::Reloader.prepare!
      true
    end
  end
end

[g8d3]

thanks @umuro .

[jaredatron]

# .pryrc checked into my project root
require 'rails/console/app'
include Rails::ConsoleMethods

[counterbeing]

that did the trick @deadlyicon 👍

[jaredatron]