Added RichBlock (half) and RichText stuff

[coder2020official]

Rich Messages

• Added support for Rich Messages, allowing bots to send highly structured text and stream AI-generated replies with seamless rich formatting.
• Added the classes RichTextBold, RichTextItalic, RichTextUnderline, RichTextStrikethrough, RichTextSpoiler, RichTextDateTime, RichTextTextMention, RichTextSubscript, RichTextSuperscript, RichTextMarked, RichTextCode, RichTextCustomEmoji, RichTextMathematicalExpression, RichTextUrl, RichTextEmailAddress, RichTextPhoneNumber, RichTextBankCardNumber, RichTextMention, RichTextHashtag, RichTextCashtag, RichTextBotCommand, RichTextAnchor, RichTextAnchorLink, RichTextReference and RichTextReferenceLink, which represent different types of rich formatted text.
• Added the class RichText, which represents rich formatted text.
• Added the class RichBlockCaption, which represents the caption of a rich formatted text.
• Added the class RichBlockTableCell, which represents a cell in a table.
• Added the class RichBlockListItem, which represents an item in a list.
• Added the classes RichBlockParagraph, RichBlockSectionHeading, RichBlockPreformatted, RichBlockFooter, RichBlockDivider, RichBlockMathematicalExpression, RichBlockAnchor, RichBlockList, RichBlockBlockQuotation, RichBlockPullQuotation, RichBlockCollage, RichBlockSlideshow, RichBlockTable, RichBlockDetails, RichBlockMap, RichBlockAnimation, RichBlockAudio, RichBlockPhoto, RichBlockVideo, RichBlockVoiceNote and RichBlockThinking, which represent different types of blocks in a rich formatted message.
• Added the class RichBlock, which represents a block in a rich formatted message.
• Added the class RichMessage, which represents a rich formatted message.
• Added the field rich_message to the class Message.
• Added the class InputRichMessage, describing a rich message to send.
• Added the class InputRichMessageContent and allowed it to be used as InputMessageContent in results of inline, guest, and Web App queries.
• Added the method sendRichMessage, allowing bots to send rich messages.
• Added the method sendRichMessageDraft, allowing bots to stream partial rich messages.
• Added the parameter rich_message to the method editMessageText, allowing bots to edit rich messages.

Join Request Queries

• Added the field supports_join_request_queries to the class User.
• Added the field guard_bot to the class ChatFullInfo.
• Added the field query_id to the class ChatJoinRequest.
• Added the method answerChatJoinRequestQuery.
• Added the method sendChatJoinRequestWebApp.

Polls

• Added the class Link and the field link to the class PollMedia.
• Added the class InputMediaLink and allowed it to be used as InputPollOptionMedia.

[coder2020official]

Added RichText stuff and half of RichBlock classes

This could've been more simplified (e.g. by having text in the init of the base class), but I chose not to display and confuse people for some classes that don't have the text attribute, for example.

Long way to go, I hope I'm on the right way

[coder2020official]

@Badiboy I think I'm done, but I will double-check & test things tomorrow; you can, however, start reviewing the code

[Badiboy]

@Badiboy I think I'm done, but I will double-check & test things tomorrow; you can, however, start reviewing the code

Thank you for your work!! I do not think I can do it before weekend, but I'll do my best.

[ranjitsingha]

@coder2020official Tried the botapi101 branch with AsyncTeleBot and hit two issues using send_rich_message. Sharing in case it helps:

1. Async send_rich_message raises TypeError on every call

AsyncTeleBot.send_rich_message forwards message_thread_id to asyncio_helper.send_rich_message:

await asyncio_helper.send_rich_message(
    self.token, chat_id, rich_message,
    business_connection_id=..., message_thread_id=message_thread_id,
    direct_messages_topic_id=..., ...)

but asyncio_helper.send_rich_message(...) has no message_thread_id parameter, so every call fails with:

TypeError: send_rich_message() got an unexpected keyword argument 'message_thread_id'

(The sync apihelper.send_rich_message has the same parameter mismatch.)

2. Parsing the response crashes on plain-string rich text

After working around (1), Message.de_json of the sendRichMessage result throws whenever a rich-text node is a plain string:

File ".../telebot/types.py", in RichText.de_json
    obj = cls.check_json(json_string)
ValueError: json_type should be a json dict or string.

Per the docs, RichText can be a plain str ("either a String for plain text, an Array of RichText, or any of the following types"), but RichText.de_json always calls check_json, which can't handle a bare string. So any successfully-sent rich message containing plain text fails to deserialize. RichText.de_json should pass str (and the array case) through instead of forcing check_json.

Minimal repro (async): await bot.send_rich_message(chat_id, types.InputRichMessage(html="<b>hi</b>")).

[coder2020official]

Hi!

Thanks for noting that--I have fixed your issue exactly; however, I am yet to address RichText being an array of RichText. I will have to test and see how it will look like.

And I'm not sure my current implementation is safe. It seems to work, though.

[coder2020official]

This should hypothetically work for arrays. Not really having the time to test--would be amazing if you could play around

[ranjitsingha]

@coder2020official — your fix works. Confirmed on dee734d: send_rich_message no longer TypeErrors, and the plain-string RichText parse is resolved.

One thing worth flagging separately, because I don't think it was obvious from how I first framed it (my original report was only about the send path): the same RichText.de_json bug also hits the receive path, where the blast radius is much larger.

When a rich_message arrives in an update — e.g. a user simply forwards a rich message to the bot, or forwards one of the bot's own rich messages back — it's parsed by Update.de_json → Message.de_json → RichMessage.de_json. On the async poller that runs inside the polling loop, and the exception is raised before the offset is advanced. So a single unparseable rich_message update:

• crashes on every get_updates cycle on the same update,
• never advances past it,
• stalls the whole bot — no updates of any type are processed until the poison update is manually skipped.

In effect it's a remotely-triggerable poller stall: anyone can send/forward rich content to any polling bot and freeze it — even if the bot never sends rich messages itself. That's actually how I hit it: an inbound forward, not a send.

# no server needed to reproduce the crash Update.de_json would hit:
from telebot.types import RichText
RichText.de_json({"type": "bold", "text": "Detail"})   # pre-fix: JSONDecodeError

7b99c65 fixes the specific string-leaf case, so the common trigger is gone. 👍 The reason I'm raising it anyway: you noted RichBlock support is still "half", and that the array handling in dee734d is untested / you're "not sure it's safe". Given the receive-side blast radius above, any rich node type that isn't yet handled will resurface the same full-poller stall — not just a failed send.

So it may be worth making the receive/parse path fail-safe while the block classes are being finished: if RichMessage.de_json can't parse something, drop it to None and keep the rest of the Message intact (bots that don't consume rich_message lose nothing), rather than letting the error propagate up and jam get_updates. That decouples "incomplete rich parser" from "bot stops entirely".

[ranjitsingha]

@coder2020official — one more of the same family (like the earlier send_rich_message / message_thread_id mismatch you fixed in 7b99c65): send_rich_message_draft raises TypeError on every call.

AsyncTeleBot.send_rich_message_draft forwards business_connection_id to the helper:

return await asyncio_helper.send_rich_message_draft(
    self.token, chat_id, draft_id, rich_message,
    message_thread_id=message_thread_id, business_connection_id=business_connection_id)

but asyncio_helper.send_rich_message_draft has no such parameter:

async def send_rich_message_draft(token, chat_id, draft_id, rich_message, message_thread_id=None):

so every call fails with:

TypeError: send_rich_message_draft() got an unexpected keyword argument 'business_connection_id'

Minimal repro (async):

await bot.send_rich_message_draft(chat_id, 1, types.InputRichMessage(html="<tg-thinking>hi</tg-thinking>"))

The sync apihelper.send_rich_message_draft(token, chat_id, draft_id, rich_message, message_thread_id=None) has the same missing parameter, so the sync TeleBot method hits it too.

Suggested fix: add business_connection_id=None to both the async and sync send_rich_message_draft helpers and include it in the payload when set (mirroring how send_rich_message handles it).

I worked around it by calling the helper directly, and the draft itself streams fine once that's bypassed.

[coder2020official]

sendrichmessagedraft shouldn't even have business connection id

[coder2020official]

I tried forwarding a rich message to the bot and there were no issues

[ranjitsingha]

I tried forwarding a rich message to the bot and there were no issues

It was fixed in dee734d

[Badiboy]

@coder2020official Sorry for been so long. Hope to review today.

[Badiboy]

String.

[Badiboy]

string

[Badiboy]

Propose to inherut it from InputMedia for consistency. Yes, I know that "media" field is required. I see two options:

1. Make "media" optional for all InputMedia-s
2. Override "init" here to avoid "media" for this class and set it to "None" inside.

First option looks more correct.

[Badiboy]

Missed fields:

[Badiboy]

Not optional here also.

[Badiboy]

No has_spoiler

[Badiboy]

Remove has_spoiler here also. And from init params.

[Badiboy]

text missed.