fix(editor): Fix an issue with an empty chat response if not in output
property
#8913
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.
Summary
This PR fixes an issue where the chat message would render as
<Empty response>
when using basic or QA chains.When rendering the chat message,
@n8n/chat
looks for it in theoutput
property of the response object. This is how we return it for agents but not for chains. So we add thetext
property fallback, and if none of them are defined, try to render a full stringified response.