ronami_core/payloads/send_location.rs
1//! Generated by `codegen_payloads`, do not edit by hand.
2
3use serde::Serialize;
4
5use crate::types::{
6 BusinessConnectionId, CallbackQueryId, EffectId, LivePeriod, Message, Recipient, ReplyMarkup,
7 ReplyParameters, SuggestedPostParameters, ThreadId, TopicId, UserId,
8};
9
10impl_payload! {
11 /// Use this method to send point on the map. On success, the sent [`Message`] is returned.
12 ///
13 /// [`Message`]: crate::types::Message
14 #[derive(Debug, PartialEq, Clone, Serialize)]
15 pub SendLocation (SendLocationSetters) => Message {
16 required {
17 /// Unique identifier for the target chat or username of the target channel (in the format `@channelusername`)
18 pub chat_id: Recipient [into],
19 /// Latitude of the location
20 pub latitude: f64,
21 /// Longitude of the location
22 pub longitude: f64,
23 }
24 optional {
25 /// Unique identifier of the business connection on behalf of which the message will be sent
26 pub business_connection_id: BusinessConnectionId,
27 /// Unique identifier for the target message thread (topic) of the forum; for forum supergroups only
28 pub message_thread_id: ThreadId,
29 /// Identifier of the direct messages topic to which the message will be sent; required if the message is sent to a direct messages chat
30 pub direct_messages_topic_id: TopicId,
31 /// The radius of uncertainty for the location, measured in meters; 0-1500
32 pub horizontal_accuracy: f64,
33 /// Period in seconds for which the location will be updated (see [Live Locations], should be between 60 and 86400, or 0x7FFFFFFF for live locations that can be edited indefinitely.
34 ///
35 /// [Live Locations]: https://telegram.org/blog/live-locations
36 pub live_period: LivePeriod,
37 /// For live locations, a direction in which the user is moving, in degrees. Must be between 1 and 360 if specified.
38 pub heading: u16,
39 /// For live locations, a maximum distance for proximity alerts about approaching another chat member, in meters. Must be between 1 and 100000 if specified.
40 pub proximity_alert_radius: u32,
41 /// Sends the message [silently]. Users will receive a notification with no sound.
42 ///
43 /// [silently]: https://telegram.org/blog/channels-2-0#silent-messages
44 pub disable_notification: bool,
45 /// Protects the contents of sent messages from forwarding and saving
46 pub protect_content: bool,
47 /// Pass `true` to allow up to 1000 messages per second, ignoring broadcasting limits for a fee of 0.1 Telegram Stars per message. The relevant Stars will be withdrawn from the bot's balance
48 pub allow_paid_broadcast: bool,
49 /// Unique identifier of the message effect to be added to the message; for private chats only
50 pub message_effect_id: EffectId,
51 /// An object containing the parameters of the suggested post to send; for direct messages chats only. If the message is sent as a reply to another suggested post, then that suggested post is automatically declined.
52 pub suggested_post_parameters: SuggestedPostParameters,
53 /// Identifier of the user who received the message
54 pub receiver_user_id: UserId,
55 /// Unique identifier of the query to be answered
56 pub callback_query_id: CallbackQueryId,
57 /// Description of the message to reply to
58 pub reply_parameters: ReplyParameters,
59 /// Additional interface options. A JSON-serialized object for an [inline keyboard], [custom reply keyboard], instructions to remove a reply keyboard or to force a reply from the user. Not supported for messages sent on behalf of a business account.
60 ///
61 /// [inline keyboard]: https://core.telegram.org/bots#inline-keyboards-and-on-the-fly-updating
62 /// [custom reply keyboard]: https://core.telegram.org/bots#keyboards
63 pub reply_markup: ReplyMarkup [into],
64 }
65 }
66}