Add way to define Sidekiq sender class

[jylamont]

This is one possible solution to #51 and #54. Essentially you can define your own SidekiqWorker class to send API requests to Vero.

Something like this...

class MyVeroSidekiqWorker < Vero::SidekiqWorker
   sidekiq_options retry: 2, queue: 'another_queue'
   sidekiq_retry_in { |count| 60 }
end

and in vero.rb

Vero::App.init do |config|
   # ...
   config.sender_class = MyVeroSidekiqWorker
end

What do you think @damienbrz, @shaneog, @lemboy, @criticerz?

[lemboy]

Yes, we did something like this - added possible use custom sidekiq worker #56.

[shaneog]

I like it. It's cleaner than the current monkey patching I'm doing.

Now, if we could remove the hard dependency on sucker_punch it would be great 👍 😄

[graphite-app]

Using eval here introduces potential security risks since it executes arbitrary Ruby code. The safer approach is to use Rails' constantize method which is specifically designed for class name resolution: api_class.to_s.constantize

Spotted by Graphite Reviewer

Is this helpful? React 👍 or 👎 to let us know.