-
Notifications
You must be signed in to change notification settings - Fork 2.4k
feat: upgrade @mcp-ui/client package and improve UI message handling
#4164
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
Changes from all commits
af87ca2
642c7ab
5e91a4c
c9993be
47ff5a8
7436c9b
d5a57bb
b1f8120
d588b65
d066e12
8ba07ad
930ccc1
d029e73
89d4edf
5602b61
26593cc
76c9303
09c122d
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -208,6 +208,7 @@ export default function GooseMessage({ | |
| toolResponse={toolResponsesMap.get(toolRequest.id)} | ||
| notifications={toolCallNotifications.get(toolRequest.id)} | ||
| isStreamingMessage={isStreaming} | ||
| append={append} | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. what does this do?
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Inside of The goal is to
@zane, do you know if there is a more elegant way to pass a prompt string to the chat engine w/out prop drilling?
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think prop drilling is ok for 2 levels like this for now but we don't have any other global state mechanism currently other than React context. So you could use context if needed. We plan on adding a global state library soon that can make things like this easier. |
||
| /> | ||
| </div> | ||
| ))} | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.
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.
had to do this, but we can remove when this issue is completely resolved MCP-UI-Org/mcp-ui#90