-
Notifications
You must be signed in to change notification settings - Fork 27
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
Automagically recognize Inputs and Outputs #11
Comments
|
So in the end, this:
becomes:
("In" becomes type-less node and "Out" becomes literaly type-less :D, therefore "Transformation" becomes implicitly output/sink node) |
There are two way out of this:
Both are equally weird solutions, so it doesn't matter which to choose. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Having a metanode like this:
One can easily omit explicit Input and Output declaration since constructed graph implicitly has this information:
By this rule, every source node without explicit Input type is an Input. And vice versa, every sink node without explicit Output type is an Output.
What to do when node is source AND sink at the same time?
The text was updated successfully, but these errors were encountered: