-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Seems that announce only runs on ActiveJob, but is that mandatory? #13
Comments
Shoryuken workers should receive those 2 args; you have to use shoryuken if not activejob, right? For us, we only use announce with activejob.
|
@kookster yeap because I can define the |
I see what you did, I think that might be fine, but I'm wishing I had a non-activeJob test project to verify - I may have to make one. |
Hi guys! me again, when I tried to create a subscriber that does not inherit from ActiveJob the gem seems that doesn't like it. For example:
So when module
Subscriber
call thedelegate_event(*args)
(L19) passes not a single argument but instead 2, thesqs_msg
and thebody
that when usingActiveJob
theShoryukenAdapter::AnnounceWorker
class received and passed only thebody
.My questions is do you want me to add a PR with this changes or this is moving out of the vision or idea that you had for the gem, in that case I understand it.
Please let me know in order to know how to proceed
Thanks!
The text was updated successfully, but these errors were encountered: