fix: fix basic markdown usage #75
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Pull Request Test Coverage Report for Build 12789272942Details
💛 - Coveralls |
kantord
force-pushed
the
fix-markdown-config
branch
3 times, most recently
from
4df842e to
5204752
Compare
kantord
force-pushed
the
fix-markdown-config
branch
from
5204752 to
63791c5
Compare
peppescg
approved these changes
Jan 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
this includes some fixes for the markdown implementation across the project
visually there isn't much difference, there are minimal adjustments. But now the component automatically takes care of proper rendering, thus fixing the broken markdown in the chats:
Record_select-area_20250115141916.mp4