"Different naming convention than the usual" - where's the usual?

Question

Telethon Chat

lonami

"Different naming convention than the usual" - where's the usual?

telegram's api calls it silent

0

31.08.2023

4 ответов

5 просмотров

lonami Автор вопроса

abdul

sorry my bad. i was migrating from API rather than...

i generally don't read the botapi docs. i don't personally like their custom layer of abstraction with telethon i aim to stay closer to how telegram actually works (which should hopefully be less confusing when you hop between mtproto libraries)

0

8 месяцев назад

abdul

oh wait i found some inconsistency here https://core.telegram.org/method/messages.sendMessage in here telegram use message keyword as to put messages, so there is no "text" keyword here the text keyword that telethon used is referenced on bot api instead of the original method https://core.telegram.org/bots/api#available-methods is there a reason?

0

8 месяцев назад

lonami Автор вопроса

abdul
oh wait i found some inconsistency here https://co...

message.message is a thing in telethon .text is a custom property which returns the formatted text .raw_text is an alias for .message to avoid the awkwardness (and have it work with event directly)

0

8 месяцев назад

abdul · Accepted Answer

abdul

sorry my bad. i was migrating from API rather than MTproto, thats why i assume disable_notification as the default convention as you seen here (https://core.telegram.org/bots/api#available-methods) instead i should be looking at this page instead (https://core.telegram.org/method/messages.sendMessage)

0

8 месяцев назад

Похожие чаты

"Different naming convention than the usual" - where's the usual?

4 ответов

Похожие вопросы