Repository navigation
feat(telegram): add Post message rendered as HTML with tags and buttons - #57
Merged
Merged
Conversation
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
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.
First step of #56: plugins need one message type that renders as a designed post on Telegram and as their existing output everywhere else.
Postmessage part: Markdown body, an optional lazily built image, hashtags, up to 3 link buttons, and a silent flag.sendPhotoorsendMessagein HTML. The body supports bold, italic, code, links, lists and quotes. Headings render as bold. Captions are cut at 1024 characters and texts at 4096. Link previews are off.Post.Fallback, so QQ output stays byte-for-byte the same.chat:topicas the chat id.No plugin sends a
Postyet.