Describe the bug
The protocol defines some types for workflos events such as pipes and forwards that do not have all the attributes so that it is possible to identify the target actor.
I suggest that we change to use the ActorId in these types
At the moment:
// Sends the output of a action of an Actor to the input of another action of an Actor// Useful for handle `pipes` pattern:// https://www.enterpriseintegrationpatterns.com/patterns/messaging/PipesAndFilters.htmlmessagePipe {
// Target Actorstringactor=1;
// Action. stringaction_name=2;
}
// Sends the input of a action of an Actor to the input of another action of an Actor// Useful for handle `content-basead router` pattern// https://www.enterpriseintegrationpatterns.com/patterns/messaging/ContentBasedRouter.htmlmessageForward {
// Target Actorstringactor=1;
// Action. stringaction_name=2;
}Improvement suggestion:
// Sends the output of a action of an Actor to the input of another action of an Actor// Useful for handle `pipes` pattern:// https://www.enterpriseintegrationpatterns.com/patterns/messaging/PipesAndFilters.htmlmessagePipe {
// Target Actoreigr.functions.protocol.actors.ActorIdactor=1;
// Action. stringaction_name=2;
}
// Sends the input of a action of an Actor to the input of another action of an Actor// Useful for handle `content-basead router` pattern// https://www.enterpriseintegrationpatterns.com/patterns/messaging/ContentBasedRouter.htmlmessageForward {
// Target Actoreigr.functions.protocol.actors.ActorIdactor=1;
// Action. stringaction_name=2;
}ping @eliasdarruda@marcellanz
Describe the bug
The protocol defines some types for workflos events such as pipes and forwards that do not have all the attributes so that it is possible to identify the target actor.
I suggest that we change to use the ActorId in these types
At the moment:
Improvement suggestion:
ping @eliasdarruda@marcellanz