refactor: improve artifact type handling and result processing #6002
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 several changes to improve the handling and processing of artifacts in the backend. The most important changes involve modifying the logic for determining the artifact type, updating the raw result processing, and refactoring the post-processing of raw data.
Improvements to artifact type determination and raw result processing:
src/backend/base/langflow/custom/custom_component/component.py
: Modified the_build_artifact
method to correctly prioritizeraw
overstatus
when determining the artifact type. Updated the_process_raw_result
method to check forstatus
after other conditions, ensuring proper handling of raw results.Refactoring of post-processing logic:
src/backend/base/langflow/schema/artifact.py
: Added adefault_message
variable to store the default success message. Refactored thepost_process_raw
method to use this variable instead of hardcoding the message, enhancing maintainability and readability. [1] [2]Language Model Output View: