Skip to main content
Using Deno in production at your company? Earn free Deno merch.
Give us feedback
Module

x/mtkruto/tl/2_types.ts>messages_SearchResultsCalendar_

Cross-runtime JavaScript library for building Telegram clients
Go to Latest
class messages_SearchResultsCalendar_
import { messages_SearchResultsCalendar_ } from "https://deno.land/x/mtkruto@0.1.190/tl/2_types.ts";

Information about found messages sent on a specific day

Constructors

new
messages_SearchResultsCalendar_(params: { inexact?: true; count: number; min_date: number; min_msg_id: number; offset_id_offset?: number; periods: Array<enums.SearchResultsCalendarPeriod>; messages: Array<enums.Message>; chats: Array<enums.Chat>; users: Array<enums.User>; })

Properties

protected
readonly
[id]: number
protected
readonly
[params]: Params
chats: Array<enums.Chat>

Mentioned chats

count: number

Total number of results matching query

optional
inexact: true

If set, indicates that the results may be inexact

messages: Array<enums.Message>

Messages

min_date: number

Starting timestamp of attached messages

min_msg_id: number

Ending timestamp of attached messages

optional
offset_id_offset: number

Indicates the absolute position of messages[0] within the total result set with count count.
This is useful, for example, if we need to display a progress/total counter (like photo 134 of 200, for all media in a chat, we could simply use photo ${offset_id_offset} of ${count}.

periods: Array<enums.SearchResultsCalendarPeriod>

Used to split the messages by days: multiple SearchResultsCalendarPeriod constructors are returned, each containing information about the first, last and total number of messages matching the filter that were sent on a specific day.
This information can be easily used to split the returned messages by day.

users: Array<enums.User>

Mentioned users

Static Properties

readonly
[name]: string
readonly
[paramDesc]: ParamDesc