activejob

It would be nice to integrate Sorbet. I have tried before in #235, but found more sharp edges than I was comfortable with.

Short-term success is having some additional manual tooling and workflows that adds value to the development process and is not burdensome to contributors.

Long-term success would be to run Sorbet type checking as part of the CI lint process (e.g. there is a clean/gree

This is a bag of thoughts issue, I encourage everyone to file more specific detailed issues and send pull requests.

• do not use keyword arguments in plain Sidekiq workers mperham/sidekiq#2372 (check if it works or not with ActiveJob)

• do not schedule jobs inside a transaction if a record created/updated inside this transaction will be directly or indirectl

Hi there, thank you for this useful gem!

I'm using it both with Resque and Sidekiq, and as the README says, in order to properly make Sidekiq queue cleanup and job death working with this gem, the patch needs to be required.

Can you please better explain how this patch works and why is it necessary?
More particularly, why is it always calling ActiveJob::Uniqueness.unlock!, that delete loc