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.6 KiB
1.6 KiB
| title | description |
|---|---|
| message | message attributes, type and example |
Constructor: message
Attributes:
| Name | Type | Required |
|---|---|---|
| id | int | Yes |
| from_id | int | Yes |
| to_id | Peer | Yes |
| fwd_from_id | int | Optional |
| fwd_date | int | Optional |
| reply_to_msg_id | int | Optional |
| date | int | Yes |
| message | string | Yes |
| media | MessageMedia | Optional |
| reply_markup | ReplyMarkup | Optional |
Type: Message
Example:
$message = ['_' => 'message', 'id' => int, 'from_id' => int, 'to_id' => Peer, 'fwd_from_id' => int, 'fwd_date' => int, 'reply_to_msg_id' => int, 'date' => int, 'message' => 'string', 'media' => MessageMedia, 'reply_markup' => ReplyMarkup];
PWRTelegram json-encoded version:
{"_": "message", "id": int, "from_id": int, "to_id": Peer, "fwd_from_id": int, "fwd_date": int, "reply_to_msg_id": int, "date": int, "message": "string", "media": MessageMedia, "reply_markup": ReplyMarkup}
Or, if you're into Lua:
message={_='message', id=int, from_id=int, to_id=Peer, fwd_from_id=int, fwd_date=int, reply_to_msg_id=int, date=int, message='string', media=MessageMedia, reply_markup=ReplyMarkup}
Usage of reply_markup
You can provide bot API reply_markup objects here.