Skip to content

Commit

Permalink
Added support for hashtag and cashtag entities with a specified chat …
Browse files Browse the repository at this point in the history
…username that opens a search for the relevant tag within the specified chat.
  • Loading branch information
coder2020official committed Nov 1, 2024
1 parent c16e264 commit cabd0cb
Showing 1 changed file with 4 additions and 5 deletions.
9 changes: 4 additions & 5 deletions telebot/types.py
Original file line number Diff line number Diff line change
Expand Up @@ -1639,11 +1639,10 @@ class MessageEntity(Dictionaryable, JsonSerializable, JsonDeserializable):
Telegram Documentation: https://core.telegram.org/bots/api#messageentity
:param type: Type of the entity. Currently, can be “mention” (@username), “hashtag” (#hashtag), “cashtag” ($USD),
“bot_command” (/start@jobs_bot),“url” (https://telegram.org), “email” ([email protected]), “phone_number” (+1-212-555-0123),
“bold” (bold text), “italic” (italic text), “underline” (underlined text), “strikethrough” (strikethrough text),
“spoiler” (spoiler message), “blockquote” (block quotation), “expandable_blockquote” (collapsed-by-default block quotation),
“code” (monowidth string), “pre” (monowidth block), “text_link” (for clickable text URLs),
:param type: Type of the entity. Currently, can be “mention” (@username), “hashtag” (#hashtag or #hashtag@chatusername), “cashtag” ($USD or $USD@chatusername),
“bot_command” (/start@jobs_bot), “url” (https://telegram.org), “email” ([email protected]), “phone_number” (+1-212-555-0123), “bold” (bold text),
“italic” (italic text), “underline” (underlined text), “strikethrough” (strikethrough text), “spoiler” (spoiler message), “blockquote” (block quotation),
“expandable_blockquote” (collapsed-by-default block quotation), “code” (monowidth string), “pre” (monowidth block), “text_link” (for clickable text URLs),
“text_mention” (for users without usernames), “custom_emoji” (for inline custom emoji stickers)
:type type: :obj:`str`
Expand Down

0 comments on commit cabd0cb

Please sign in to comment.