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
When using LibreChat's search feature, the search results correctly highlight the search terms in bold. However, when copying the search results using the provided copy button, the copied text erroneously includes the Markdown syntax for bold (**), which should not be present in the copied content.
Steps to Reproduce
Open LibreChat and use the search feature to search for a specific term.
Observe that the search term is highlighted in bold in the search results.
Click the copy button to copy the search result.
Paste the copied text into any text editor or input field.
What browsers are you seeing the problem on?
No response
Relevant log output
No response
Screenshots
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
The search results are emboldened because they literally have the markdown syntax for bold when retrieved from meilisearch. I suppose I can remove the bold effect entirely
The search results are emboldened because they literally have the markdown syntax for bold when retrieved from meilisearch. I suppose I can remove the bold effect entirely
Thank you, it would be great if it could be removed, as I need to quickly copy the previous prompt and do not want LLM to be affected by unexpected markdown syntax
What happened?
When using LibreChat's search feature, the search results correctly highlight the search terms in bold. However, when copying the search results using the provided copy button, the copied text erroneously includes the Markdown syntax for bold (**), which should not be present in the copied content.
Steps to Reproduce
What browsers are you seeing the problem on?
No response
Relevant log output
No response
Screenshots
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: