-
Notifications
You must be signed in to change notification settings - Fork 298
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
[REFACTOR] update UnsupportedContent
rendering
#2819
Comments
Good call @musale |
In a case where we want developers to provide their own logic to render the content (replace an adaptive card, for instance), we should provide a |
|
Describe the bug
Currently, rendering the
UnsupportedContent
component is done by stringifying the component and appending it as a string in the content property. This brings in state mutation of the props that is not advised.To Reproduce
Steps to reproduce the behavior:
microsoft-graph-toolkit/packages/mgt-chat/src/utils/chat.tsx
Lines 15 to 24 in 2a61bd7
Expected behavior
Rendered
UnsupportedContent
component as a react component. Wrap it inChatMessage
orChatMyMessage
components from@fluentui/react-components
. Add the chat message header customizations for a similar look to the rest of the messages. Remove any state mutations on the props passed inonRenderMessage
.Additional Context
ChatMessage
andChatMyMessage
The text was updated successfully, but these errors were encountered: