-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Refactor DataFilterComponent inputs #4524
Conversation
CodSpeed Performance ReportMerging #4524 will degrade performances by 14.46%Comparing Summary
Benchmarks breakdown
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, you can use the Component tests with this one. We can merge it after #4526
), | ||
MessageInput( | ||
StrInput( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
StrInput( | |
MessageTextInput( |
@@ -1,7 +1,7 @@ | |||
from typing import Any | |||
|
|||
from langflow.custom import Component | |||
from langflow.io import DataInput, DropdownInput, MessageInput, Output | |||
from langflow.io import DataInput, DropdownInput, Output, StrInput |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
from langflow.io import DataInput, DropdownInput, Output, StrInput | |
from langflow.io import DataInput, DropdownInput, Output, MessageTextInput |
…nstead of StrInput
6edf51d
to
84c12f6
Compare
This pull request refactors the inputs of the DataFilterComponent to use the StrInput class instead of the MessageInput class. The StrInput class is more appropriate for handling string inputs, and this change improves the clarity and consistency of the code.