Total Complexity | 1 |
Total Lines | 30 |
Duplicated Lines | 0 % |
Changes | 0 |
1 | <?php |
||
11 | class inlineQuery extends types { |
||
|
|||
12 | /** Keep all of properties which has sub properties */ |
||
13 | private const subs = ['from' => 'BPT\types\user', 'location' => 'BPT\types\location']; |
||
14 | |||
15 | /** Unique identifier for this query */ |
||
16 | public string $id; |
||
17 | |||
18 | /** Sender */ |
||
19 | public user $from; |
||
20 | |||
21 | /** Text of the query (up to 256 characters) */ |
||
22 | public string $query; |
||
23 | |||
24 | /** Offset of the results to be returned, can be controlled by the bot */ |
||
25 | public string $offset; |
||
26 | |||
27 | /** |
||
28 | * Optional. Type of the chat, from which the inline query was sent. Can be either “sender” for a private |
||
29 | * chat with the inline query sender, “private”, “group”, “supergroup”, or “channel”. The chat |
||
30 | * type should be always known for requests sent from official clients and most third-party clients, unless the |
||
31 | * request was sent from a secret chat |
||
32 | */ |
||
33 | public string $chat_type; |
||
34 | |||
35 | /** Optional. Sender location, only for bots that request user location */ |
||
36 | public location $location; |
||
37 | |||
38 | |||
39 | public function __construct(stdClass $update) { |
||
43 |
The issue could also be caused by a filter entry in the build configuration. If the path has been excluded in your configuration, e.g.
excluded_paths: ["lib/*"]
, you can move it to the dependency path list as follows:For further information see https://scrutinizer-ci.com/docs/tools/php/php-scrutinizer/#list-dependency-paths