fix: Enhance extract_class_name function to identify Component subclasses #4492
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 improvements to the
extract_class_name
function in thesrc/backend/base/langflow/utils/validate.py
file. The changes enhance the function's robustness and readability by adding type annotations, a detailed docstring, and additional error handling.Improvements to
extract_class_name
function:code
parameter is a string and the function returns a string.try-except
block to catchSyntaxError
exceptions and raise aValueError
with a descriptive message.bases
of class definitions and checking for inheritance fromComponent
orLC
. This can be improved to a more generic solution but it fixes the problem for now