Resolve "Output node conditions"
1 unresolved thread
1 unresolved thread
Closes #18 (closed)
Input nodes and output nodes can have default link attributes which will be used whenever making links with a super-graph. The link attributes in the super graph have priority.
Edited by Wout De Nolf
Merge request reports
Activity
assigned to @denolf
added 1 commit
- c78a88a9 - allow adding default link attributes to the input and output nodes of a graph
requested review from @payno
added 1 commit
- c339afc1 - allow adding default link attributes to the input and output nodes of a graph
mentioned in issue ewoksppf#5 (closed)
87 83 88 89 In case the referenced nodes are graphs, the node inside that graph needs to be references with the `"sub_node"` key. 90 For example 84 For example for a graph with nodes `"id1"` (normal node) and `"id2"` (graph with an input node `"alias3"`): 91 85 92 86 .. code-block:: json 93 87 94 88 { 95 89 "graph": { 96 90 "input_nodes": [ 97 {"id": "alias1", "node": "name1", "sub_node": "name3"}, 98 {"id": "alias2", "node": "name2", "sub_node": "name4"}, 91 {"id": "alias1", "node": "id1"}, 92 {"id": "alias2", "node": "id2", "sub_node": "alias3"}, 99 93 ] Viewing the example make me a bit confused especially about
id
andnode
:- id values are aliasXX
- node values are idXXX
Sorry but reading it again make me wonder if we shouldn't call:
- id -> super_graph_id: mandatory
- node -> graph_id (or local_id or id): mandatory
- sub_node -> sub_node_id : optional
And maybe add a scheme with this graph and a super graph and a subgraph to make it 100% clear.
We had a discussion on this: #13 (closed) Feel free to re-open the discussion.
mentioned in commit 7b424695
Please register or sign in to reply