Skip to content

Feature Request: support branch check to run when have a nextNode with too many entry node from different branches #1005

@oneWalker

Description

@oneWalker

For example, when we have a graph on this below;

graph TD
    start --> nodea
    nodea --> node1-con
    nodea --> node2
    node1-con --> node1-1
    node1-con --> nodem
    node2 --> nodem
    node2 --> node2-1
    node1-1 --> node1-1-1
    node1-1-1 --> nodec
    nodem --> nodec
    node2-1 --> nodec
    nodec --> 'end'

Loading

or

graph TD
    start --> nodea
    nodea --> node1-con
    nodea --> node2
    node1-con --> node1-1
    node1-con --> nodec
    node2 --> nodec
    node2 --> node2-1
    node1-1 --> node1-1-1
    node1-1-1 --> nodec
    node2-1 --> nodec
    nodec --> 'end'
Loading

when the node is executed in nodem or nodec can be calculated that it's allowed to run.

Currently, I find the nextNode of condtionalEdgeNode is triggered by the condtionNode without checking the other dependent node. And the currentNode only check all the dependant nodes without removing the useless one when the other branch.

I achieved it by sharing the context content and the skipped strategy . However, I met another problem that may need to trigger the next nodes once. #1006

I'm very glad to share the implement code of my project with the official developer so that we can contribute to the library better.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions