fix: inconsistent text table result for Message Type output #6633
Conversation
This file contains 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
dosubot
bot
added
the
size:XS
github-actions
bot
added
bug
|
Thank you @Cristhianzl |
thanks to have attention on that! |
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 pull request includes a change to the
src/backend/base/langflow/custom/custom_component/component.pyfile. The change focuses on the_process_raw_resultmethod to simplify the processing of raw results.Codebase simplification:
src/backend/base/langflow/custom/custom_component/component.py: Removed the condition checking the length ofself.outputsand the return ofself.statusorself.extract_data(result), simplifying the_process_raw_resultmethod to always callself.extract_data(result).