mirror of
https://github.com/aiogram/aiogram.git
synced 2026-04-08 16:37:47 +00:00
Adding new code-generator (Butcher) (#1069)
* Re-generate types * Re-generate methods (only attributes) * Added enums * Base init generator * Added butcher configs * Fixed tests, bump butcher * Added changelog * Added enum docs * Added templates for docs index * Re-generate bot class, remove deprecated methods
This commit is contained in:
parent
c7779abc50
commit
d034c1ba9f
387 changed files with 32036 additions and 3144 deletions
131
.butcher/types/InlineQueryResultLocation/entity.json
Normal file
131
.butcher/types/InlineQueryResultLocation/entity.json
Normal file
|
|
@ -0,0 +1,131 @@
|
|||
{
|
||||
"meta": {
|
||||
"deprecated": false
|
||||
},
|
||||
"group": {
|
||||
"title": "Inline mode",
|
||||
"anchor": "inline-mode"
|
||||
},
|
||||
"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.",
|
||||
"annotations": [
|
||||
{
|
||||
"type": "String",
|
||||
"description": "Type of the result, must be location",
|
||||
"html_description": "<td>Type of the result, must be <em>location</em></td>",
|
||||
"rst_description": "Type of the result, must be *location*\n",
|
||||
"name": "type",
|
||||
"required": true
|
||||
},
|
||||
{
|
||||
"type": "String",
|
||||
"description": "Unique identifier for this result, 1-64 Bytes",
|
||||
"html_description": "<td>Unique identifier for this result, 1-64 Bytes</td>",
|
||||
"rst_description": "Unique identifier for this result, 1-64 Bytes\n",
|
||||
"name": "id",
|
||||
"required": true
|
||||
},
|
||||
{
|
||||
"type": "Float number",
|
||||
"description": "Location latitude in degrees",
|
||||
"html_description": "<td>Location latitude in degrees</td>",
|
||||
"rst_description": "Location latitude in degrees\n",
|
||||
"name": "latitude",
|
||||
"required": true
|
||||
},
|
||||
{
|
||||
"type": "Float number",
|
||||
"description": "Location longitude in degrees",
|
||||
"html_description": "<td>Location longitude in degrees</td>",
|
||||
"rst_description": "Location longitude in degrees\n",
|
||||
"name": "longitude",
|
||||
"required": true
|
||||
},
|
||||
{
|
||||
"type": "String",
|
||||
"description": "Location title",
|
||||
"html_description": "<td>Location title</td>",
|
||||
"rst_description": "Location title\n",
|
||||
"name": "title",
|
||||
"required": true
|
||||
},
|
||||
{
|
||||
"type": "Float number",
|
||||
"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",
|
||||
"name": "horizontal_accuracy",
|
||||
"required": false
|
||||
},
|
||||
{
|
||||
"type": "Integer",
|
||||
"description": "Period in seconds for which the location can be updated, should be between 60 and 86400.",
|
||||
"html_description": "<td><em>Optional</em>. Period in seconds for which the location can be updated, should be between 60 and 86400.</td>",
|
||||
"rst_description": "*Optional*. Period in seconds for which the location can be updated, should be between 60 and 86400.\n",
|
||||
"name": "live_period",
|
||||
"required": false
|
||||
},
|
||||
{
|
||||
"type": "Integer",
|
||||
"description": "For live locations, a direction in which the user is moving, in degrees. Must be between 1 and 360 if specified.",
|
||||
"html_description": "<td><em>Optional</em>. For live locations, a direction in which the user is moving, in degrees. Must be between 1 and 360 if specified.</td>",
|
||||
"rst_description": "*Optional*. For live locations, a direction in which the user is moving, in degrees. Must be between 1 and 360 if specified.\n",
|
||||
"name": "heading",
|
||||
"required": false
|
||||
},
|
||||
{
|
||||
"type": "Integer",
|
||||
"description": "For live locations, a maximum distance for proximity alerts about approaching another chat member, in meters. Must be between 1 and 100000 if specified.",
|
||||
"html_description": "<td><em>Optional</em>. For live locations, a maximum distance for proximity alerts about approaching another chat member, in meters. Must be between 1 and 100000 if specified.</td>",
|
||||
"rst_description": "*Optional*. For live locations, a maximum distance for proximity alerts about approaching another chat member, in meters. Must be between 1 and 100000 if specified.\n",
|
||||
"name": "proximity_alert_radius",
|
||||
"required": false
|
||||
},
|
||||
{
|
||||
"type": "InlineKeyboardMarkup",
|
||||
"description": "Inline keyboard attached to the message",
|
||||
"html_description": "<td><em>Optional</em>. <a href=\"/bots/features#inline-keyboards\">Inline keyboard</a> attached to the message</td>",
|
||||
"rst_description": "*Optional*. `Inline keyboard <https://core.telegram.org/bots/features#inline-keyboards>`_ attached to the message\n",
|
||||
"name": "reply_markup",
|
||||
"required": false
|
||||
},
|
||||
{
|
||||
"type": "InputMessageContent",
|
||||
"description": "Content of the message to be sent instead of the location",
|
||||
"html_description": "<td><em>Optional</em>. Content of the message to be sent instead of the location</td>",
|
||||
"rst_description": "*Optional*. Content of the message to be sent instead of the location\n",
|
||||
"name": "input_message_content",
|
||||
"required": false
|
||||
},
|
||||
{
|
||||
"type": "String",
|
||||
"description": "Url of the thumbnail for the result",
|
||||
"html_description": "<td><em>Optional</em>. Url of the thumbnail for the result</td>",
|
||||
"rst_description": "*Optional*. Url of the thumbnail for the result\n",
|
||||
"name": "thumb_url",
|
||||
"required": false
|
||||
},
|
||||
{
|
||||
"type": "Integer",
|
||||
"description": "Thumbnail width",
|
||||
"html_description": "<td><em>Optional</em>. Thumbnail width</td>",
|
||||
"rst_description": "*Optional*. Thumbnail width\n",
|
||||
"name": "thumb_width",
|
||||
"required": false
|
||||
},
|
||||
{
|
||||
"type": "Integer",
|
||||
"description": "Thumbnail height",
|
||||
"html_description": "<td><em>Optional</em>. Thumbnail height</td>",
|
||||
"rst_description": "*Optional*. Thumbnail height\n",
|
||||
"name": "thumb_height",
|
||||
"required": false
|
||||
}
|
||||
],
|
||||
"category": "types"
|
||||
}
|
||||
}
|
||||
2
.butcher/types/InlineQueryResultLocation/replace.yml
Normal file
2
.butcher/types/InlineQueryResultLocation/replace.yml
Normal file
|
|
@ -0,0 +1,2 @@
|
|||
bases:
|
||||
- InlineQueryResult
|
||||
Loading…
Add table
Add a link
Reference in a new issue