fix(telegram): strip markdown formatting on overflow fallback (#43441) - #43590
Closed
kyssta-exe wants to merge 1 commit into
Closed
fix(telegram): strip markdown formatting on overflow fallback (#43441)#43590kyssta-exe wants to merge 1 commit into
kyssta-exe wants to merge 1 commit into
Conversation
alt-glitch
added
type/bug
Collaborator
|
Duplicate of #33304 — that earlier open PR uses the same approach: strip raw markdown in the MarkdownV2 fallback paths so literal |
Contributor
Author
This was referenced Jul 30, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes #43441. When MarkdownV2 parsing fails during overflow split in forum topics, the fallback path was sending raw Markdown text without parse_mode, causing literal bold and backtick markers to appear. Now strips formatting markers before sending as plain text.