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
The first group (optionally) matches the language ( line 298 val language = ... )
The second group has all the lines in the code block, including all the prepended whitespaces ( line 299 val codeBody = ... )
So my suspicion is that codeBody is trimmed (removing all prepending- and appending whitespaces, newlines etc.) later on. That would explain why it only happens on the first line of the code block.
But the only use of trim() I can find is in MarkdownRules.kt in a override fun parse() function:
val classes = matcher.group(2)?.trim()?.split(' ')
..and I have zero idea if it's related in any way.
There is also the possibility that this bug is outside of SimpleAST .. ?
The text was updated successfully, but these errors were encountered:
I encountered the same issue. Additionally, in code blocks inside of embeds, tabs (\t) do not get rendered in-between text.
The above two messages are renditions of the same text, and there is also a leading space in front of the first character that doesn't get rendered.
Problem
When I send a message where the first characters, in the first line, in a code block, is whitespaces, like this:
Then the prepended whitespaces is removed from the first line, when displayed on Android and message looks like this:
On Discord Desktop and iOS app, the same message is rendered the way I would expect it:
A Wild Guess Appears
I tested this markdown code block regex, but the matching seems to work correctly:
val language = ...
)val codeBody = ...
)So my suspicion is that
codeBody
is trimmed (removing all prepending- and appending whitespaces, newlines etc.) later on. That would explain why it only happens on the first line of the code block.But the only use of
trim()
I can find is in MarkdownRules.kt in aoverride fun parse()
function:..and I have zero idea if it's related in any way.
There is also the possibility that this bug is outside of SimpleAST .. ?
The text was updated successfully, but these errors were encountered: