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:
Alex Root Junior 2022-11-21 01:06:55 +02:00 committed by GitHub
parent c7779abc50
commit d034c1ba9f
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
387 changed files with 32036 additions and 3144 deletions

View file

@ -0,0 +1,91 @@
{
"meta": {
"deprecated": false
},
"group": {
"title": "Inline mode",
"anchor": "inline-mode"
},
"object": {
"anchor": "inlinequeryresultcachedvoice",
"name": "InlineQueryResultCachedVoice",
"description": "Represents a link to a voice message stored on the Telegram servers. By default, this voice message will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the voice message.\nNote: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.",
"html_description": "<p>Represents a link to a voice message stored on the Telegram servers. By default, this voice message 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 voice message.</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 link to a voice message stored on the Telegram servers. By default, this voice message will be sent by the user. Alternatively, you can use *input_message_content* to send a message with the specified content instead of the voice message.\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 voice",
"html_description": "<td>Type of the result, must be <em>voice</em></td>",
"rst_description": "Type of the result, must be *voice*\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": "String",
"description": "A valid file identifier for the voice message",
"html_description": "<td>A valid file identifier for the voice message</td>",
"rst_description": "A valid file identifier for the voice message\n",
"name": "voice_file_id",
"required": true
},
{
"type": "String",
"description": "Voice message title",
"html_description": "<td>Voice message title</td>",
"rst_description": "Voice message title\n",
"name": "title",
"required": true
},
{
"type": "String",
"description": "Caption, 0-1024 characters after entities parsing",
"html_description": "<td><em>Optional</em>. Caption, 0-1024 characters after entities parsing</td>",
"rst_description": "*Optional*. Caption, 0-1024 characters after entities parsing\n",
"name": "caption",
"required": false
},
{
"type": "String",
"description": "Mode for parsing entities in the voice message caption. See formatting options for more details.",
"html_description": "<td><em>Optional</em>. Mode for parsing entities in the voice message caption. See <a href=\"#formatting-options\">formatting options</a> for more details.</td>",
"rst_description": "*Optional*. Mode for parsing entities in the voice message caption. See `formatting options <https://core.telegram.org/bots/api#formatting-options>`_ for more details.\n",
"name": "parse_mode",
"required": false
},
{
"type": "Array of MessageEntity",
"description": "List of special entities that appear in the caption, which can be specified instead of parse_mode",
"html_description": "<td><em>Optional</em>. List of special entities that appear in the caption, which can be specified instead of <em>parse_mode</em></td>",
"rst_description": "*Optional*. List of special entities that appear in the caption, which can be specified instead of *parse_mode*\n",
"name": "caption_entities",
"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 voice message",
"html_description": "<td><em>Optional</em>. Content of the message to be sent instead of the voice message</td>",
"rst_description": "*Optional*. Content of the message to be sent instead of the voice message\n",
"name": "input_message_content",
"required": false
}
],
"category": "types"
}
}

View file

@ -0,0 +1,6 @@
bases:
- InlineQueryResult
annotations:
parse_mode:
value: UNSET