-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JsonProperty fix for Webhook #1302
base: dev
Are you sure you want to change the base?
Conversation
…r classes in the same package. It helps Webhook to return a correctly serialized json result.
…elegrambots/meta/api/methods the way it is done in other classes in the same package. It helps Webhook to return a correctly serialized json result.
How will you be returning the images/documents in the json? |
A semicolon were missing in the Standalone reply code. The reply signature changed and needs a BiConsumer<BaseAbilityBot, Update> instead of Consumer<Update> in the Ability reply
According to Telegram API Docs, you can send InputFile using its |
Add getMessageId to MaybeInaccessibleMessage According to https://core.telegram.org/bots/api#maybeinaccessiblemessage
…ed from 'Boolean' to 'String' (according to TelegramBotAPI Official Documentation). (rubenlagus#1315)
* fix force=true for WriteAccessAllowed * + test and fixtures on write access allowed
* Fix path for GetMyName method * Add missing sticker methods from API 6.6 * Fix possible NPE in InputSticker validation * Add ReplyParameters to SendInvoice API method * Removed mysterious fields in SetChatTitle
c4394aa
to
7df1524
Compare
bc4fd52
to
65c33e0
Compare
68a6f61
to
5fc7d88
Compare
Annotated fields with missing JsonProperty in
org/telegram/telegrambots/meta/api/methods
the way it is done in other classes in the same package.It helps Webhook to return a correctly serialized json result.