You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I love the depth of the configuration options in Langflow and how the new toggle button for tweaks builds the entire json structure. That said, there isn't a description field in the json that helps to identify what the component is doing.
When you click on Tweaks in the API window, it's so easy to understand what component does what.
But there is nothing to tell you what the components are from the configuration.
This is a challenge for my application, which is designed to make it easy to invoke, chain, and consume Langflow workflows from the command line.
Can a description/name field be added to all the tweaks override settings so that it's possible to understand what each component is intended to do just from the configuration file? Ideally, the default description aligns with the accordion drop-downs in the API window (screenshot above).
Now, when I invoke my command and populate the autocomplete overrides, it pulls key names
If something like the above was implemented, I could change it so the values in the autocomplete are pulled from the description
instead of seeing - "TextInput-P3cGK.template" it would be "Workers Context.template".
I can implement some level of a solution for this within my application, but it seems like something that might be useful in the Langflow project as a whole.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I love the depth of the configuration options in Langflow and how the new toggle button for tweaks builds the entire json structure. That said, there isn't a description field in the json that helps to identify what the component is doing.
When you click on Tweaks in the API window, it's so easy to understand what component does what.
But there is nothing to tell you what the components are from the configuration.
This is a challenge for my application, which is designed to make it easy to invoke, chain, and consume Langflow workflows from the command line.
Can a description/name field be added to all the tweaks override settings so that it's possible to understand what each component is intended to do just from the configuration file? Ideally, the default description aligns with the accordion drop-downs in the API window (screenshot above).
Now, when I invoke my command and populate the autocomplete overrides, it pulls key names
If something like the above was implemented, I could change it so the values in the autocomplete are pulled from the description
I can implement some level of a solution for this within my application, but it seems like something that might be useful in the Langflow project as a whole.
Thanks,
Nick
Beta Was this translation helpful? Give feedback.
All reactions