-
Notifications
You must be signed in to change notification settings - Fork 276
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
methods to clear cached classes after reload!
is called
#855
Conversation
methods to clear cached classes after `reload!` is called
Any news on when this PR might get released on Rubygems? Right now, using |
We definitely want to release a 5.1 soon. I've been producing some screencasts for the gems and the latest screencasts require some features in master, so those will need to be made publicly accessible. |
To give a clearer answer: I expect we'll at least do an RC that'll be in the next week or two, one way or another. |
Ah, gotcha, so this is going out as a point release and not a patch. Thank you for the work, I'll watch for the RC! |
Ah, right. I'm not sure if @subvertallchris planned to do a patch (I know he's been busy with work lately), but obviously it will go out with a point release ;) Thanks for the patience |
I think a patch release would be a good idea. A few people are locked to the specific commit that fixed it because they need what it provides, I think it would help them out. I'll take care of it when I have a few minutes today and will post here when it's done. |
👍 Thank you! |
Just released 5.0.15 with this. Let us know if you have any trouble. |
@subvertallchris: CHANGELOG? ;) |
It works great - thanks! 🎉 |
This appears to correct the root cause of #717 and possibly neo4jrb/devise-activegraph#16. It uses the
before_remove_const
method fired by ActiveSupport'sreload!
to wipe cached references to classes. It's possible others are still lurking but this will be a start.