Skip to content
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

Add an after_all_successful_events callback #799

Open
alecvn opened this issue Oct 13, 2022 · 0 comments
Open

Add an after_all_successful_events callback #799

alecvn opened this issue Oct 13, 2022 · 0 comments

Comments

@alecvn
Copy link

alecvn commented Oct 13, 2022

It seems to me a callback is required which one can assign to all events and only triggers if the event was actually successful. The after_all_events callback is fairly lacking in that, as far as I can tell, there is no way of knowing whether the events were successful or not.

An after_all_successful_events callback, which is called after all the individual events' success callbacks would be ideal for this scenario.

If one then needs to wait for the data to actually be persisted to the database one can use something like AfterCommitEverywhere.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant