Skip to content
#

telegram-bot-api

Here are 838 public repositories matching this topic...

teloxide
WaffleLapkin
WaffleLapkin commented Aug 6, 2020

Current documentation (send_photo):

Pass InputFile::File to send a photo that exists on the Telegram servers (recommended), pass an InputFile::Url for Telegram to get a .webp file from the Internet, or upload a new one using InputFile::FileId. More info on Sending Files ».

There are 3 problems with this:

  1. There is no mention of InputFile::Memory
  2. ::File is meant to be use
vjgarciag96
vjgarciag96 commented May 17, 2020

In the past, to serialize the ParseMode enum we were using an additional String attribute modeName with the value to be used in the "serialization". After #72 we've started to use the @SerializedName annotation as the preferred way for enums serialization (supported both by our Gson and Retrofit configurations) which is transparent for us.

Therefore, it would be really nice to repla

marcelgarus
marcelgarus commented Apr 30, 2020

I like the distinction of telegram and teledart – one is a simple typed wrapper around web requests, the other one a full-fledged powerful API that uses the capabilities of object-oriented programming. Some aspects like the inline mode are really great, but I think other parts could be a bit better.
For example, most requests still need to be made through the teledart instance with the exce

Improve this page

Add a description, image, and links to the telegram-bot-api topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the telegram-bot-api topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.