-
Notifications
You must be signed in to change notification settings - Fork 125
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
Allow to use any background job library to handle async jobs #381
Conversation
end | ||
|
||
class MyAsyncHandler | ||
@@received = nil |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm afraid this and other class variables will make this test brittle
@@ -1,27 +1,25 @@ | |||
module RailsEventStore |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ActiveJobDispatcher
is RailsEventStore::
, however AsyncDispatcher
can be moved to RubyEventStore::
and be used in non-rails scenarios.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We still use there AsyncProxyStrategy::AfterCommit
which uses ActiveRecord
but maybe this should stay in RailsEventStore::
and only AsyncProxyStrategy::Inline
should moved with AsyncDispatcher
to RubyEventStore::
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Looks good (and I am happy it was merged) except for one thing. How about
? |
@mpraglowski do you plan updating the documentation in a separate PR? |
|
btw. docs can live in master via toggle |
@paneq yep - just after some refactorings mentioned here |
Breaking change: signature of dispatcher's proxy strategy is changed