Every app with core patches feels a little bit different.
Ruby monkey patch gem.
There are many cases where it s fine to monkey patch but it should definitely not be your first weapon of choice.
It ensures that the monkey patching happens before the first request.
We re in the future and with github and bundler there is now rarely a need to monkey patch ruby code in your applications.
Classes can be reopened at any time.
We can give mopsy new methods even after she has already been created.
Monkey patching is so 2010.
Rails application config to prepare do devisecontroller class eval do your new methods here end end.
Instantly publish your gems and then install them use the api to find out more about available gems.
If you don t want the patch anymore just comment out that line.
Actually monkey patch datetime datetime.
Become a contributor and improve the site yourself.
Or perhaps you need to monkey patch a class you own.
When you monkey patch core classes you add to the core ruby apis.
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.
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.