Daniil Gentili
e4a326e552
* refactor * Apply fixes from StyleCI * Implement https and http transport, add support for new req_pq_multi, send pending acks and objects in containers along with the next method call, remove dependency on the socket extension. * Apply fixes from StyleCI * Make types with empty constructors optional, fix phar archives (fixes #217) * Apply fixes from StyleCI * Update to layer 75 * Update github pages gemfile.lock
1.1 KiB
1.1 KiB
| title | description |
|---|---|
| inputBotInlineMessageMediaGeo | inputBotInlineMessageMediaGeo attributes, type and example |
Constructor: inputBotInlineMessageMediaGeo
Attributes:
| Name | Type | Required |
|---|---|---|
| geo_point | InputGeoPoint | Optional |
| reply_markup | ReplyMarkup | Optional |
Type: InputBotInlineMessage
Example:
$inputBotInlineMessageMediaGeo = ['_' => 'inputBotInlineMessageMediaGeo', 'geo_point' => InputGeoPoint, 'reply_markup' => ReplyMarkup];
PWRTelegram json-encoded version:
{"_": "inputBotInlineMessageMediaGeo", "geo_point": InputGeoPoint, "reply_markup": ReplyMarkup}
Or, if you're into Lua:
inputBotInlineMessageMediaGeo={_='inputBotInlineMessageMediaGeo', geo_point=InputGeoPoint, reply_markup=ReplyMarkup}
Usage of reply_markup
You can provide bot API reply_markup objects here.