Path function gets passed the graphs state_schema instead of the previous nodes returned state #1654
Unanswered
tgrimminger
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I found out about this while trying to use a private state as described in the documentation here.
My final goal was to have a private state for part of my graph so that I don't have to pollute the main state with additional fields that are only need for a small part of the graph.
Here is a minimum reproducible example, hopefully this makes things more clear:
In this example the

special_node
returns a StateB (the private state), which thedecider
is supposed to act on, instead the decider gets a StateA (the graphs state_schema-> the base-state).Here I would expect that the
decider
function gets a StateB, as this is the state that was returned by the last node before it. This is the way it works between two nodes (see documentation). But instead, it gets passed a StateA.Is this by design (conditional edges can only use the base-state?) or is this a Bug?
Beta Was this translation helpful? Give feedback.
All reactions