TelegramBot\Entities\InlineQuery

Complexity

Total Complexity

2

Size/Duplication

Total Lines	27
Duplicated Lines	0 %

Importance

Changes

0

2 Methods

Rating	Name	Duplication	Size	Complexity
A	answer()	0	6	1
A	subEntities()	0	5	1

<?php

namespace TelegramBot\Entities;

use TelegramBot\Entities\InlineQuery\InlineQueryResult;
use TelegramBot\Entity;
use TelegramBot\Request;

/**
 * Class InlineQuery
 *
 * @link https://core.telegram.org/bots/api#inlinequery
 *
 * @method string   getId()         Unique identifier for this query
 * @method User     getFrom()       Sender
 * @method Location getLocation()   Optional. Sender location, only for bots that request user location
 * @method string   getQuery()      Text of the query (up to 512 characters)
 * @method string   getOffset()     Offset of the results to be returned, can be controlled by the bot
 * @method string   getChatType()   Optional. Type of the chat, from which the inline query was sent. Can be either “sender” for a private chat with the inline query sender, “private”, “group”, “supergroup”, or “channel”. The chat type should be always known for requests sent from official clients and most third-party clients, unless the request was sent from a secret chat
 */
class InlineQuery extends Entity
{

    /**
     * Answer this inline query with the passed results.
     *
     * @param InlineQueryResult[] $results
     * @param array $data
     *
     * @return Response
     */
    public function answer(array $results, array $data = []): Response
    {
        return Request::answerInlineQuery(array_merge([
            'inline_query_id' => $this->getId(),
            'results' => $results,
        ], $data));
    }

    /**
     * {@inheritdoc}
     */
    protected function subEntities(): array
    {
        return [
            'from' => User::class,
            'location' => Location::class,
        ];
    }

}