It ensures that the monkey patching happens before the first request.
Ruby monkey patch gem.
Monkey patching is the dangerous yet frequently useful technique of re opening existing classes to change or add to their behavior.
If you don t want the patch anymore just comment out that line.
Become a contributor and improve the site yourself.
Classes can be reopened at any time.
Instantly publish your gems and then install them use the api to find out more about available gems.
Actually monkey patch datetime datetime.
Rails application config to prepare do devisecontroller class eval do your new methods here end end.
This effect is similar to after initialize hook but ensures that monkey patching is reapplied in development mode after a reload in prod mode the result is identical.
Or perhaps you need to monkey patch a class you own.
Writing a gem send define method method missing instance eval monkey patching for great justice.
Ruby has a very beautiful syntax and so it can be tempting to monkey patch a class to turn some ugly method call into something that is more readable.
We re in the future and with github and bundler there is now rarely a need to monkey patch ruby code in your applications.
Because ruby is an interpreted language objects are open and can be modified at runtime.
There are many cases where it s fine to monkey patch but it should definitely not be your first weapon of choice.
Every app with core patches feels a little bit different.