Commit Graph

25 Commits (4656d9d8926ad7b8bc5bf0f50163c7bcb2ea1db9)

Author SHA1 Message Date
aiden e5cf14aeea Method name and structs specified. 8 years ago
aiden 2558381794 GetUserProfilePhotos added 8 years ago
aiden d18a89193d getChatAdministrators added 8 years ago
Peng-Jie 1e02352d3f Sequence Location field 8 years ago
Sebastian Schepens 587ba1a4dc
add AnswerCallbackQuery 8 years ago
Vlad Lukyanov 15e5df6636 Add MessageEntity support 8 years ago
Vlad Lukyanov 977e1d90f3 gofmt 8 years ago
Vlad Lukyanov 4b79f3ff1b merge with upstream 8 years ago
Nick Groenen 46992b037b Improve support for inline queries
These changes make it possible to set custom options when responding to
inline queries, as described on
https://core.telegram.org/bots/api#answerinlinequery.

It also includes all the (non-cached) inline result types as described
at https://core.telegram.org/bots/api#inlinequeryresult.

Some remarks:
* The internals of sendCommand have changed. It now expects a
  JSON-serializable object. Instead of doing GET requests with
  URL-encoded query parameters it now POSTS JSON directly.
* Because of the above, sendFile() has changed as well. It now expects a
* `map[string]string` which it will internally convert to URL encoded
  form values.
* Respond has been deprecated in favor of the new AnswerInlineQuery
  function. It is only kept for backward compatibility.
* A dependency on https://github.com/mitchellh/hashstructure has been
  introduced in order to generate automatic IDs for inline results.
8 years ago
Steven Berlanga 4b2c1f976c adding documentation to callback struct 8 years ago
Vlad Lukyanov 0a92c6c68b Added Venue message support by calling SendVenue(recipient Recipient, venue *Venue, options *SendOptions) 8 years ago
Steven Berlanga 72e84f5ab5 Adding support for inline keyboard buttons 8 years ago
Ian Byrd 061a651188
This commit adds an inline mode implementation and resolves #28.
Only article results supported so far.
9 years ago
Ronmi Ren 143777fbe0 Channel support and change chat_id size
* Chage signature of "Destination()", because we need send username in "chat_id" when
  sending message to channel.
* By telegram API document, chat id is "not exceeding 1e13 by absolute value" which
  needs int64 to store it.
9 years ago
Ian Byrd 4103e705b0
Fixing critical API issue; resolves #26 9 years ago
Ilya Kowalewski 72ce8fae88 Fixing #21 issue, introducing Recipient interface 9 years ago
Ilya Kowalewski 74d63a4754 Merging #20 into tucnak:master from aladine:patch-3 9 years ago
Anton Volodin e38f2bd56c Another code bloat fixes 9 years ago
Ilya Kowalewski 40c91ee0b4 Added some API and tests 9 years ago
Ilya Kowalewski eaf9b17a54 Achieving final satisfaction with golint 9 years ago
Ilya Kowalewski e041242bb2 Fixed a bunch of lint issues 9 years ago
Ilya Kowalewski 6a4863ece8 Sending photos, API improvements 9 years ago
Ilya Kowalewski d2435c4688 Message forwarding 9 years ago
Ilya Kowalewski 43bbb6b396 All message types and replying/forwarding from API covered. 9 years ago
Ilya Kowalewski fa51650dad A little more documentation, code cleanup 9 years ago