fix(telegram): set parse_mode for markdown messages#245
Open
fix(telegram): set parse_mode for markdown messages#245
Conversation
postMessage and editMessage only set parse_mode when a card was present, causing markdown messages to render as plain text with visible formatting characters. Now also sets parse_mode when the message has a markdown field. Closes #226
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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.
postMessageandeditMessageonly setparse_modewhen a card was present, causing{ markdown: "..." }messages to render as plain text with visible formatting characters. Now also setsparse_modeto"Markdown"when the message has amarkdownfield.Closes #226