-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
feat: conditional_node #723
Conversation
I was unable to create a more modular solution due to the requirement of state key knowledge for condition evaluation. The node must access and evaluate specific keys within the state to function correctly, particularly when parsing and evaluating complex conditions that may include built-in functions or expressions involving state variables. Abstracting this functionality further would limit the node's ability to perform its intended purpose, as it would not have the necessary context to evaluate conditions accurately. Therefore, this implementation strikes a balance between modularity and the practical necessity of accessing state-specific information. I welcome any suggestions on how to improve this within the constraints |
ok please can you provide me an example of condition? |
@ekinsenler btw I think we have implemented the depth search |
Condition can be set on
Or we can just set the |
Cool, is that already in beta? |
thx, can u add it in the examples? |
yes, the name is something like depth search graph |
btw @ekinsenler can u remove smart scraper cond graph and add the conditional node if a condition is present? can you do for all the graphs? |
@VinciGit00 that graph was mainly to demonstrate the usage of the |
🎉 This PR is included in version 1.26.0-beta.5 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
conditional_node
implementation with a custom condition that can be set in thenode_config
. Also integrated into the the existing graph for the demonstration.