fix: robust JSON parsing in Iteration node #4603
Closed
Conversation
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
|
can you give me a demo agentflow to replicate the error? |
|
[BUG] Iteration Node is not parsing the Flow variable, it remains as a string. #4600 |
|
somebody aprove this sh*t |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR fixes a bug in the Iteration node where JSON input variables were not being parsed correctly. The node now robustly parses stringified JSON (including those with escape characters), allowing proper iteration over arrays and objects. This prevents errors when passing variables or JSON strings as input to the Iteration node.
How to test:
Pass a variable or stringified JSON array/object to the Iteration node’s input.
The node should correctly iterate over each element without JSON parsing errors.