Socket
Socket
Sign inDemoInstall

@grammyjs/types

Package Overview
Dependencies
Maintainers
1
Versions
84
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@grammyjs/types - npm Package Compare versions

Comparing version 3.8.1 to 3.9.0

2

markup.d.ts

@@ -18,3 +18,3 @@ import type { ChatAdministratorRights, User } from "./manage.js";

interface CallbackButton extends AbstractInlineKeyboardButton {
/** Data to be sent in a callback query to the bot when button is pressed, 1-64 bytes. Not supported for messages sent on behalf of a Telegram Business account. */
/** Data to be sent in a callback query to the bot when the button is pressed, 1-64 bytes */
callback_data: string;

@@ -21,0 +21,0 @@ }

{
"name": "@grammyjs/types",
"version": "3.8.1",
"version": "3.9.0",
"description": "Telegram Bot API type declarations for grammY",

@@ -5,0 +5,0 @@ "main": "mod.js",

@@ -102,1 +102,69 @@ import type { User } from "./manage.js";

}
/** This object describes the state of a revenue withdrawal operation. Currently, it can be one of
- RevenueWithdrawalStatePending
- RevenueWithdrawalStateSucceeded
- RevenueWithdrawalStateFailed */
export type RevenueWithdrawalState = RevenueWithdrawalStatePending | RevenueWithdrawalStateSucceeded | RevenueWithdrawalStateFailed;
/** The withdrawal is in progress. */
export interface RevenueWithdrawalStatePending {
/** Type of the state, always “pending” */
type: "pending";
}
/** The withdrawal succeeded. */
export interface RevenueWithdrawalStateSucceeded {
/** Type of the state, always “succeeded” */
type: "succeeded";
/** Date the withdrawal was completed in Unix time */
date: number;
/** An HTTPS URL that can be used to see transaction details */
url: string;
}
/** The withdrawal failed and the transaction was refunded. */
export interface RevenueWithdrawalStateFailed {
/** Type of the state, always “failed” */
type: "failed";
}
/** This object describes the source of a transaction, or its recipient for outgoing transactions. Currently, it can be one of
- TransactionPartnerFragment
- TransactionPartnerUser
- TransactionPartnerOther */
export type TransactionPartner = TransactionPartnerFragment | TransactionPartnerUser | TransactionPartnerOther;
/** Describes a withdrawal transaction with Fragment. */
export interface TransactionPartnerFragment {
/** Type of the transaction partner, always “fragment” */
type: "fragment";
/** State of the transaction if the transaction is outgoing */
withdrawal_state?: RevenueWithdrawalState;
}
/** Describes a transaction with a user. */
export interface TransactionPartnerUser {
/** Type of the transaction partner, always “user” */
type: "user";
/** Information about the user */
user: User;
}
/** Describes a transaction with an unknown source or recipient. */
export interface TransactionPartnerOther {
/** Type of the transaction partner, always “other” */
type: "other";
}
/** Describes a Telegram Star transaction. */
export interface StarTransaction {
/** Unique identifier of the transaction. Coincides with the identifer of the original transaction for refund transactions. Coincides with SuccessfulPayment.telegram_payment_charge_id for successful incoming payments from users. */
id: string;
/** Number of Telegram Stars transferred by the transaction */
amount: number;
/** Date the transaction was created in Unix time */
date: number;
/** Source of an incoming transaction (e.g., a user purchasing goods or services, Fragment refunding a failed withdrawal). Only for incoming transactions */
source?: TransactionPartner;
/** Receiver of an outgoing transaction (e.g., a user for a purchase refund, Fragment for a withdrawal). Only for outgoing transactions */
receiver?: TransactionPartner;
}
/** Contains a list of Telegram Star transactions. */
export interface StarTransactions {
/** The list of transactions */
transactions: StarTransaction[];
}

Sorry, the diff of this file is too big to display

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc