This came from a newbie that is learning Rails. He had the console running while adding a model and a mailer in another terminal session, then he went to the and tried to create a new record of that model but instead got a NameError. He expend and hour trying to figure out what was going on until h…

It’s a natural idea to have, but this is done to avoid surprises. Let me explain. Reloading can’t happen in the middle of a session. Imagine a script run got class definitions changed in the middle of the execution, that would have impredictable consequences. In a console session is the same, you r…

I remember this one taking me a little while to learn too, way back when. Can we drill down a little more on the logic you expect? One way I could see of implementing the thing you’re describing: Have listen or similar detect a code change. Have it output a message to the Rails console like “Code…

I think having an in-line notice that the code was changed, and to reload if you want those updates in the session, would be great. Doubt it’s going to be annoying even to experienced devs. If you have an active console session, and you’re changing classes in the background, you probably want to see…

I get why this should not happen automatically on every change. I’ve been doing Rails for a while, and always remember that I need to reload con code change. Some sort of warning in the console prompt should not be annoying and helpful for newcomers. irb(main*reload):001:0>

If the console is aware that changes to the code have been made, there is really no reason to not just reload at that point. [image] DHH: If you have an active console session, and you’re changing classes in the background, you probably want to see those changes reflected!

How about adding rails console --auto-reload for those (like me) who want to avoid typing reload! every time while being aware of the caveats? NB: I was so far unaware of reload! and had been hitting Ctrl-D + rails c every time. An info notice might be quite helpful.

[image] markvanlan: If the console is aware that changes to the code have been made, there is really no reason to not just reload at that point. A warning here from my experience: Even seasoned Ruby programmers do not fully understand how classes, modules, and constants work, and how decouple…

I agree with the reasons for not automated reloading. Then again, I can still remember that it was confusing when I started with Rails, and moreover, it was hard to find relevant information. For a long time I thought I was doing it wrong, closing and restarting the console. Maybe the solution is …

[image] emcoding: Maybe the solution is not changing the behaviour, but document it. FWIW, this is documented . The autoloading guide is important to get somewhat familiar with this aspect of the framework.

Actually, the stale object point could be entirely sidestepped if instead of reload, we reboot. Simply start a brand new console session within the current one. Blow away all existing object references.

Console is not aware of code changes

A May Of WTFs

DHH (DHH) May 16, 2020, 8:19pm 18

Like --auto-reboot and the reminder too! Totally agree that you can get away with a lot of magic when you tell people what tricks are being performed.

Topic		Replies	Views
how can I get the CONSOLE (./script/console) to automatically detect/handle changes to code that I change??? rubyonrails-talk	1	186	December 21, 2008
Why do I have to reload the Console rubyonrails-talk	4	196	November 9, 2006
reload! in console? rubyonrails-talk	3	162	September 16, 2010
howto reload changes using script/console ? rubyonrails-talk	0	133	August 30, 2010
console does not reload rubyonrails-talk	5	204	June 3, 2008

Console is not aware of code changes

Related topics

More Resources