In my application, we don't allow monkey-patching of the language. We've found that various libraries tend to monkey-patch in incompatible ways, and it's very hard to excise dependence on a particular monkey-patch once it's in the codebase.
I've made monkey-patching opt-in rather than opt-out, but can change that around if necessary.
If I'm correct, this turns off monkey patching by default, correct? If so, I would need this patch to be inverted. A lot of people use this feature, and it would pull the rug out from underneath them.
Rename configatron.rb -> core.rb
Make monkey patching depend on how configatron is required
Yep, that's right (wasn't sure if opt-out would be necessary, per my note above).
Behavior inverted. The interface is that you load 'configatron/core' to not get the monkey-patches (similar to how sinatra and state_machine do it, for instance).
This caused a lot of merge conflicts with the laster master version. Can you please resolve in your branch and then re-open the PR? Thanks.