Closed Edouard-chin closed 6 years ago
I think that makes sense. We probably want to make that opt in though.
Sounds good, planning to implement that and polish this gem sometimes before June 15th where it's planned to be opensource it as well as talk about it in the engineering blog
A lot of gems (resque-scheduler, minitest, dogapi ...) doesn't use
ActiveSupport::Deprecation
and instead just trigger a deprecation usingKernel.warn
. We have no way on our side to keep track of these deprecations.My idea was to implement something similar to the ruby-warning gem and catch any warning that might be deprecations (most of the time the warning is prefixed with the
[DEPRECATION]
tag) and monkey patch theWarning
module to instead useActiveSupport::Deprecation.warn
whenever a deprecation is triggered.WDYT @rafaelfranca @wvanbergen