Defer event handler and process router init until after subscribed #138
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
slashdotdash
force-pushed
the
feature/subscribed-init
branch
4 times, most recently
from
015d574
to
da5b150
Compare
Event store adapter sends a `{:subscribed, subscription}` message once the subscription has successfully subscribed.
This can be used to defer initialisation for event handlers, such as the `init/0` callback, and process routers.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Expect event store adapters to send a
{subscribed, subscription}message once successfully subscribed.This is used to defer initialisation for event handlers, such as calling the
init/0callback, and process routers. One benefit of deferringinit/0is that it will only run once, irrespective of how many nodes are running your app and the event handler.