Made Delayed::Backend::ActiveRecord::Job
class load lazily
#245
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In Rails, classes like
ActiveRecord::Base
are designed to be loaded lazily. If a gem eagerly loads classes when required, as this gem did, it can cause issues where configurations written inconfig/initializers/*.rb
for ActiveRecord are not applied properly. To avoid this, theActiveSupport.on_load(:active_record) do ... end
block is used to delay loading theActiveRecord::Base
class andDelayed::Backend::ActiveRecord::Job
class until after Rails has fully initialized.In this commit, I wrapped the existing
Delayed::Backend::ActiveRecord::Job
class definition in a block to minimize changes. However, it might be better to separateDelayed::Backend::ActiveRecord::Configuration
into a dedicated file for easier management.