feat: Conditional edges#2
Open
gluonfield wants to merge 2 commits into
Open
Conversation
devalexandre
approved these changes
May 5, 2024
|
wait for this merge :) |
|
Hi, |
good question :) |
Same Question. YES, that's quite import I think |
|
For information : I forked the repo to avoid conflict with go dependencies (package name) while waiting for the PR to be merged. It will be removed as soon as the PR is merged into @tmc's repo : Temp repository link |
|
I think this project died |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Support for conditional edges
Motivation: langgraph-js/py supports conditional edges where the edge to target node calculated dynamically at runtime.
Looking forward to hear your thoughts.