-
Notifications
You must be signed in to change notification settings - Fork 147
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
[Fix #677] Atomic produce and consume actions #826
Conversation
9021bd7
to
d7aabdc
Compare
Signed-off-by: Francisco Javier Tirado Sarti <[email protected]>
Signed-off-by: Francisco Javier Tirado Sarti <[email protected]>
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.
Many thanks for the work! ❤️
Just a couple of pita comments to discuss😄
Signed-off-by: Francisco Javier Tirado Sarti <[email protected]>
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.
Great work, thank you!
Could I please ask you to update the roadmap.md
to include the changes brought by this PR?
This is already there in the roadmap for 0.9 |
@fjtirado You are right! Sorry about that! |
Merging this PR as per contribution rules: it has been out for more than 3 weeks, and has already been approved by the required majority. |
Many thanks for submitting your Pull Request ❤️!
Please specify parts of this PR update:
Discussion or Issue link:
Fixes #677
What this PR does / why we need it:
Separated produceEventRef from consumeEventRef, removing eventRef, and promoting both to first class actions.
Remove kind property from event definition. Therefore the same event definition can be both used for consumption and publishing. if needed.
Special notes for reviewers:
I have couple of doubts about naming notation that I reflected as comments.
Additional information: