Edouard CHIN 9eb4b4ed01 Fix deprecation being thrown at boot time: ... - ### Problem In rails/rails@bbfab0b33a I introduced a change which outputs a deprecation whenever a class inherits from ActiveJob::Base. This has the negative effect to trigger a massive amount of deprecation at boot time especially if your app is eagerloaded (like it's usually the case on CI). Another issue with this approach was that the deprecation will be output no matter if a job define a `after_perform` callbacks i.e. ```ruby class MyJob < AJ::Base before_enqueue { throw(:abort) } end # This shouldn't trigger a deprecation since no after callbacks are defined # The change in 6.2 will be already safe for the app. ``` ### Solution Trigger the deprecation only when a job is abort (during enqueuing or performing) AND a `after_perform` callback is defined on the job.		2019-12-13 03:25:03 +01:00
..
active_job	Fix deprecation being thrown at boot time:	2019-12-13 03:25:03 +01:00
rails/generators/job	Strip duplicated suffixes more strictly	2018-04-22 14:30:07 +09:00
active_job.rb	Bump license years for 2019	2018-12-31 10:24:38 +07:00