Added full support of Bot API 7.1 (#1417)

* Added full support of Bot API 7.1

* Added changelog
This commit is contained in:
Alex Root Junior 2024-02-16 23:44:35 +02:00 committed by GitHub
parent e5176b4434
commit 75323ac8c3
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
72 changed files with 702 additions and 461 deletions

View file

@ -7,9 +7,9 @@
"object": {
"anchor": "inlinequeryresultlocation",
"name": "InlineQueryResultLocation",
"description": "Represents a location on a map. By default, the location will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the location.\nNote: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.",
"html_description": "<p>Represents a location on a map. By default, the location will be sent by the user. Alternatively, you can use <em>input_message_content</em> to send a message with the specified content instead of the location.</p><p><strong>Note:</strong> This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.</p>",
"rst_description": "Represents a location on a map. By default, the location will be sent by the user. Alternatively, you can use *input_message_content* to send a message with the specified content instead of the location.\n**Note:** This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.",
"description": "Represents a location on a map. By default, the location will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the location.",
"html_description": "<p>Represents a location on a map. By default, the location will be sent by the user. Alternatively, you can use <em>input_message_content</em> to send a message with the specified content instead of the location.</p>",
"rst_description": "Represents a location on a map. By default, the location will be sent by the user. Alternatively, you can use *input_message_content* to send a message with the specified content instead of the location.",
"annotations": [
{
"type": "String",
@ -28,7 +28,7 @@
"required": true
},
{
"type": "Float number",
"type": "Float",
"description": "Location latitude in degrees",
"html_description": "<td>Location latitude in degrees</td>",
"rst_description": "Location latitude in degrees\n",
@ -36,7 +36,7 @@
"required": true
},
{
"type": "Float number",
"type": "Float",
"description": "Location longitude in degrees",
"html_description": "<td>Location longitude in degrees</td>",
"rst_description": "Location longitude in degrees\n",
@ -52,7 +52,7 @@
"required": true
},
{
"type": "Float number",
"type": "Float",
"description": "The radius of uncertainty for the location, measured in meters; 0-1500",
"html_description": "<td><em>Optional</em>. The radius of uncertainty for the location, measured in meters; 0-1500</td>",
"rst_description": "*Optional*. The radius of uncertainty for the location, measured in meters; 0-1500\n",