-
Notifications
You must be signed in to change notification settings - Fork 15
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
Broadcast execution completed #1023
Conversation
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.
LGTM
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.
Just a tiny thing then we can merge
1291218
to
ab558cd
Compare
ab558cd
to
5052cab
Compare
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 @fabriziosestito ,
Let's use the action function instead of importing the action key and creating the payload manually
faedcf7
to
7cb31b4
Compare
7cb31b4
to
e0531e5
Compare
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.
LGTM
Adds the updated execution completed action dispatch when the BE receives an execution completed event from wanda.
NOTE:
I had to add the channel and the callback manually and couldn't rely on the
registerEvents
utility function since the name of the action and the message sent to the phoenix channel differs.Also, I'd like to use action constants instead of generating the name of the action so I will track a debt to track an improvement on this side.