Replies: 2 comments
-
@aakrem The issue is currently not clear at all (although I totally agree that there is a problematic). I am not able to understand your proposal. Can you please explain the following: Can you please provide some context?
a what? Can you please provide more examples of UI components that we would like to provide in the future, and where do you see the current solution failing?
This line comes out of nowhere. What do you mean here? Maybe a before and after example? |
Beta Was this translation helpful? Give feedback.
-
I am converting this to discussion |
Beta Was this translation helpful? Give feedback.
-
The code here and here requires refactoring.
At some point it will be very challenging to build sophisticated ui components (A component that includes a InputParam and TextParam )
The reason of having that code is the way sdk returns the x-parameter, which is based on data types; boolean string integer...
As these parameters are mainly definitions that will be used in ui one solution could be is to add another
component
key in all SDK parameters. And of course remove the logic behindtype
.SDK Code
LLM App Code
Then in the playground what we can do is to display sdk parameters per component instead of if-elses based on data type.
Beta Was this translation helpful? Give feedback.
All reactions