-
-
Notifications
You must be signed in to change notification settings - Fork 893
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
custom html component render in a wrong way #889
Comments
@byk11 could you share the HTML/markdown you are using? |
This comment has been minimized.
This comment has been minimized.
@ChristianMurphy thank you for your reply.
![]() |
@byk11 could share your content in a code block? ```
example <my-think>test</my-think>
``` |
@ChristianMurphy sure!
|
@byk11 thanks for adding the code block. <my-think>
# think **about** something,think about something
think `about` something,think about something
</my-think> rendered think about something,think about somethingthink |
This comment has been minimized.
This comment has been minimized.
Hi! Thanks for reaching out! Because we treat issues as our backlog, we close issues that are questions since they don’t represent a task to be completed. See our support docs for how and where to ask questions. Thanks, |
@ChristianMurphy I want to render a custom Think components ![]()
@ChristianMurphy thank you. I want to render a custom think component to display what AI is thinking about. The content is from AI. Maybe I can add a '\n' before , but is there any better resolution to cover more scenarios?I found that the following three situations cannot be displayed normally.
![]() |
A few thoughts:
|
Initial checklist
Affected package
"react-markdown": "^8.0.5" "rehype-raw": "^7.0.0",
Steps to reproduce
Actual behavior
Expected behavior
think about something,think about somethingthink about something,think about something
think component only wrap his children
Runtime
https://remarkjs.github.io/react-markdown/#html-in-markdown
Package manager
pnpm@8
Operating system
mac
Build and bundle tools
No response
The text was updated successfully, but these errors were encountered: