Handle graph-definition syntax for edges #27
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Enable optional specification of edges between pipeline-element outputs and pipeline-element inputs.
Example graph:
has pipeline definition graph syntax:
Note that output names must be fully-qualified, e.g. "B.b_out_1" instead
of "b_out_1". This is due to the graph traversal not yet handling edges
defined between B and C in the example graph, only between A and B, and
between A and C.
Use of
map_out_nodes
in_process_map_out
andmap_in_nodes
in_process_map_in
are commented out because of this issue with the traversal. Rather than completely change the structure ofmap_in_nodes
andmap_out_nodes
, I've left them and added a new structureedge_definitions
, with the aim of making this easier to review.