fix: exclude none conversational fields in output#631
Merged
Conversation
JoshParkSJ
approved these changes
Feb 25, 2026
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
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.
https://uipath.atlassian.net/browse/JAR-9364
Before:
The conversational-agent graph would output
Nonefields in theterminate_node, which would eventually be serialized into an empty dict (which is a separate discussion, code here and thread here).After:
This change simply excludes the None fields from being emitted which is better in my opinion than emitting
{}ornull, since these fields could confuse users doing evaluations.Note the lack of
isTranscript, name, isIncomplete