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
Describe the bug
Testing the chat flow in samples/js-chatbot, going into the chatBotFlow in the DevUI brings up an inscrutable schema and input box that I'm unable to figure out. I think the provided input is missing a required text field, but I'm not sure where.
To repo, check out the js-chatbot at main and run npm run setup && npm run start and try to invoke the flow through the DevUI
The text was updated successfully, but these errors were encountered:
I verified this is rendering the schema exactly as defined. It's just really complex. What do you think we should do here on the Dev UI side?
For better or worse, its exposing a "prompt" object. It can just be a string. It's actually pretty simple though in practice. I assume whoever wrote this code would know what to do in the Dev UI, since they have the context.
@i2amsam I don't think there is a PO dev ui ask here. But possibly, the team should prioritize simplifying the sample to make it more approachable? WDYT?
Yeah, maybe this is two things. Agreed neither is P0
Bug in the chatbot sample instead, looking at it, I don't think the more complex input types are used.
Our JSON Schema approach doesn't scale up to the complexity that PartsSchema is not getting to, and maybe we should revisit UX patterns for the complex schemas.
Describe the bug
Testing the chat flow in samples/js-chatbot, going into the
chatBotFlow
in the DevUI brings up an inscrutable schema and input box that I'm unable to figure out. I think the provided input is missing a required text field, but I'm not sure where.To repo, check out the js-chatbot at
main
and runnpm run setup && npm run start
and try to invoke the flow through the DevUIThe text was updated successfully, but these errors were encountered: