mirror of
https://github.com/rails/rails.git
synced 2022-11-09 12:12:34 -05:00
bbfab0b33a
- ### Problem
```ruby
MyJob < ApplicationJob
before_enqueue { throw(:abort) }
after_enqueue { # enters here }
end
```
I find AJ behaviour on after_enqueue and after_perform callbacks
weird as they get run even when the callback chain is halted.
It's counter intuitive to run the after_enqueue callbacks even
though the job wasn't event enqueued.
### Solution
In Rails 6.2, I propose to make the new behaviour the default
and stop running after callbacks when the chain is halted.
For application that wants this behaviour now or in 6.1
they can do so by adding the `config.active_job.skip_after_callbacks_if_terminated = true`
in their configuration file.
|
||
|---|---|---|
| .. | ||
| abort_before_enqueue_job.rb | ||
| application_job.rb | ||
| callback_job.rb | ||
| disable_log_job.rb | ||
| gid_job.rb | ||
| hello_job.rb | ||
| inherited_job.rb | ||
| kwargs_job.rb | ||
| logging_job.rb | ||
| multiple_kwargs_job.rb | ||
| nested_job.rb | ||
| overridden_logging_job.rb | ||
| prefixed_job.rb | ||
| provider_jid_job.rb | ||
| queue_adapter_job.rb | ||
| queue_as_job.rb | ||
| rescue_job.rb | ||
| retry_job.rb | ||
| thread_job.rb | ||
| timezone_dependent_job.rb | ||
| translated_hello_job.rb | ||