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
User-Story Node with multiple output handles #105
Conversation
[API] Kudos, SonarCloud Quality Gate passed! |
[Executor] Kudos, SonarCloud Quality Gate passed! |
The changes in the Executor will wrap the results of every node in an Object. The Object contains a Field for every outgoingHandle and saves the result there. If in the Future Nodes with diferent Outputs will be created, they can be differenciated by the Outgoing Handle ID. |
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.
Some ideas/change suggestions.
@@ -10,7 +10,7 @@ export interface ScriptNode { | |||
* | |||
* @param node to execute | |||
* @param inputs of the node as an object, with the handle ids as the keys and the inputs as the values | |||
* @returns the output of the JavaScript function | |||
* @returns the output of the JavaScript function wraped into an object in fields of the outgoingHandle IDs |
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.
typo: wrapped
. Also: Call it inputs
everywhere if there might be multiple inputs (check other files too please).
[Identity] Kudos, SonarCloud Quality Gate passed! |
[Editor] Kudos, SonarCloud Quality Gate passed! |
…ub.com/Agile-Waterfall-Inc/flooq into user-story/node-multiple-output-handle
[Executor] Kudos, SonarCloud Quality Gate passed! |
Related Issues
Definition of Done
Definition of more than Done (optional)