fix(after_unlock): regression from #707 #737
Merged
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.
Background
#707 introduced a regression where the instance level
after_unlock
callback is no longer being called. This was due to the change of usingitem[CLASS]
instead ofworker_class
to setjob_class
inSidekiqUniqueJobs::Middelware#call
.item[CLASS]
is a string, where asworker_class
can be either an instance, or the class itself. For the instance levelafter_unlock
to work, we needjob_class
to be an instance of the worker.This fixes the issue by switching back to setting
job_class
toworker_class
Changelog