Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

grammy

Package Overview
Dependencies
Maintainers
0
Versions
120
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

grammy - npm Package Compare versions

Comparing version 1.25.2 to 1.26.0

46

out/composer.d.ts

@@ -415,6 +415,6 @@ import { type CallbackQueryContext, type ChatTypeContext, type ChosenInlineResultContext, type CommandContext, Context, type GameQueryContext, type HearsContext, type InlineQueryContext, type MaybeArray, type PreCheckoutQueryContext, type ReactionContext, type ShippingQueryContext, type StringWithSuggestions } from "./context.js";

* Registers middleware for the ChosenInlineResult by the given id or ids.
* ChosenInlineResult represents a result of an inline query that was
* chosen by the user and sent to their chat partner. Check out
* https://core.telegram.org/bots/api#choseninlineresult to read more
* about chosen inline results.
* ChosenInlineResult represents a result of an inline query that was chosen
* by the user and sent to their chat partner. Check out
* https://core.telegram.org/bots/api#choseninlineresult to read more about
* chosen inline results.
*

@@ -433,9 +433,10 @@ * ```ts

/**
* Registers middleware for pre-checkout queries. Telegram sends a pre-checkout
* query to your bot whenever a user has confirmed their payment and shipping
* details. You bot will then receive all information about the order and
* has to respond within 10 seconds with a confirmation of whether everything
* is alright (goods are available, etc.) and the bot is ready to proceed
* with the order. Check out https://core.telegram.org/bots/api#precheckoutquery
* to read more about pre-checkout queries.
* Registers middleware for pre-checkout queries. Telegram sends a
* pre-checkout query to your bot whenever a user has confirmed their
* payment and shipping details. You bot will then receive all information
* about the order and has to respond within 10 seconds with a confirmation
* of whether everything is alright (goods are available, etc.) and the bot
* is ready to proceed with the order. Check out
* https://core.telegram.org/bots/api#precheckoutquery to read more about
* pre-checkout queries.
*

@@ -454,9 +455,10 @@ * ```ts

/**
* Registers middleware for shipping queries. If you sent an invoice requesting
* a shipping address and the parameter _is_flexible_ was specified, Telegram
* will send a shipping query to your bot whenever a user has confirmed their
* shipping details. You bot will then receive the shipping information and
* can respond with a confirmation of whether delivery to the specified address
* is possible. Check out https://core.telegram.org/bots/api#shippingquery to
* read more about shipping queries.
* Registers middleware for shipping queries. If you sent an invoice
* requesting a shipping address and the parameter _is_flexible_ was
* specified, Telegram will send a shipping query to your bot whenever a
* user has confirmed their shipping details. You bot will then receive the
* shipping information and can respond with a confirmation of whether
* delivery to the specified address is possible. Check out
* https://core.telegram.org/bots/api#shippingquery to read more about
* shipping queries.
*

@@ -734,4 +736,4 @@ * ```ts

* defined in one place, so that they have the correct type when passed to
* `bot.chosenInlineResult` in a different place. For instance, this allows for more
* modular code where handlers are defined in separate files.
* `bot.chosenInlineResult` in a different place. For instance, this allows for
* more modular code where handlers are defined in separate files.
*/

@@ -744,4 +746,4 @@ export type ChosenInlineResultMiddleware<C extends Context> = Middleware<ChosenInlineResultContext<C>>;

* defined in one place, so that they have the correct type when passed to
* `bot.preCheckoutQuery` in a different place. For instance, this allows for more
* modular code where handlers are defined in separate files.
* `bot.preCheckoutQuery` in a different place. For instance, this allows for
* more modular code where handlers are defined in separate files.
*/

@@ -748,0 +750,0 @@ export type PreCheckoutQueryMiddleware<C extends Context> = Middleware<PreCheckoutQueryContext<C>>;

@@ -432,6 +432,6 @@ "use strict";

* Registers middleware for the ChosenInlineResult by the given id or ids.
* ChosenInlineResult represents a result of an inline query that was
* chosen by the user and sent to their chat partner. Check out
* https://core.telegram.org/bots/api#choseninlineresult to read more
* about chosen inline results.
* ChosenInlineResult represents a result of an inline query that was chosen
* by the user and sent to their chat partner. Check out
* https://core.telegram.org/bots/api#choseninlineresult to read more about
* chosen inline results.
*

@@ -452,9 +452,10 @@ * ```ts

/**
* Registers middleware for pre-checkout queries. Telegram sends a pre-checkout
* query to your bot whenever a user has confirmed their payment and shipping
* details. You bot will then receive all information about the order and
* has to respond within 10 seconds with a confirmation of whether everything
* is alright (goods are available, etc.) and the bot is ready to proceed
* with the order. Check out https://core.telegram.org/bots/api#precheckoutquery
* to read more about pre-checkout queries.
* Registers middleware for pre-checkout queries. Telegram sends a
* pre-checkout query to your bot whenever a user has confirmed their
* payment and shipping details. You bot will then receive all information
* about the order and has to respond within 10 seconds with a confirmation
* of whether everything is alright (goods are available, etc.) and the bot
* is ready to proceed with the order. Check out
* https://core.telegram.org/bots/api#precheckoutquery to read more about
* pre-checkout queries.
*

@@ -475,9 +476,10 @@ * ```ts

/**
* Registers middleware for shipping queries. If you sent an invoice requesting
* a shipping address and the parameter _is_flexible_ was specified, Telegram
* will send a shipping query to your bot whenever a user has confirmed their
* shipping details. You bot will then receive the shipping information and
* can respond with a confirmation of whether delivery to the specified address
* is possible. Check out https://core.telegram.org/bots/api#shippingquery to
* read more about shipping queries.
* Registers middleware for shipping queries. If you sent an invoice
* requesting a shipping address and the parameter _is_flexible_ was
* specified, Telegram will send a shipping query to your bot whenever a
* user has confirmed their shipping details. You bot will then receive the
* shipping information and can respond with a confirmation of whether
* delivery to the specified address is possible. Check out
* https://core.telegram.org/bots/api#shippingquery to read more about
* shipping queries.
*

@@ -484,0 +486,0 @@ * ```ts

@@ -94,2 +94,3 @@ import { type Context } from "./context.js";

readonly location: {};
readonly paid_media: {};
readonly entities: {

@@ -217,2 +218,3 @@ readonly mention: {};

readonly location: {};
readonly paid_media: {};
readonly entities: {

@@ -308,2 +310,3 @@ readonly mention: {};

readonly location: {};
readonly paid_media: {};
readonly entities: {

@@ -399,2 +402,3 @@ readonly mention: {};

readonly location: {};
readonly paid_media: {};
readonly entities: {

@@ -526,2 +530,3 @@ readonly mention: {};

readonly location: {};
readonly paid_media: {};
readonly entities: {

@@ -649,2 +654,3 @@ readonly mention: {};

readonly location: {};
readonly paid_media: {};
readonly entities: {

@@ -651,0 +657,0 @@ readonly mention: {};

@@ -268,2 +268,3 @@ "use strict";

location: {},
paid_media: {},
entities: ENTITY_KEYS,

@@ -270,0 +271,0 @@ caption_entities: ENTITY_KEYS,

/// <reference types="node" />
import { type ApiMethods as ApiMethodsF, type InputMedia as InputMediaF, type InputMediaAnimation as InputMediaAnimationF, type InputMediaAudio as InputMediaAudioF, type InputMediaDocument as InputMediaDocumentF, type InputMediaPhoto as InputMediaPhotoF, type InputMediaVideo as InputMediaVideoF, type InputSticker as InputStickerF, type Opts as OptsF } from "@grammyjs/types";
import { type ApiMethods as ApiMethodsF, type InputMedia as InputMediaF, type InputMediaAnimation as InputMediaAnimationF, type InputMediaAudio as InputMediaAudioF, type InputMediaDocument as InputMediaDocumentF, type InputMediaPhoto as InputMediaPhotoF, type InputMediaVideo as InputMediaVideoF, type InputPaidMedia as InputPaidMediaF, type InputPaidMediaPhoto as InputPaidMediaPhotoF, type InputPaidMediaVideo as InputPaidMediaVideoF, type InputSticker as InputStickerF, type Opts as OptsF } from "@grammyjs/types";
import { type ReadStream } from "fs";

@@ -72,1 +72,9 @@ export * from "@grammyjs/types";

export type InputMediaDocument = InputMediaDocumentF<InputFile>;
/** This object describes the paid media to be sent. Currently, it can be one of
- InputPaidMediaPhoto
- InputPaidMediaVideo */
export type InputPaidMedia = InputPaidMediaF<InputFile>;
/** The paid media to send is a photo. */
export type InputPaidMediaPhoto = InputPaidMediaPhotoF<InputFile>;
/** The paid media to send is a video. */
export type InputPaidMediaVideo = InputPaidMediaVideoF<InputFile>;
{
"name": "grammy",
"description": "The Telegram Bot Framework.",
"version": "1.25.2",
"version": "1.26.0",
"author": "KnorpelSenf",

@@ -20,3 +20,3 @@ "license": "MIT",

"dependencies": {
"@grammyjs/types": "3.9.0",
"@grammyjs/types": "3.10.0",
"abort-controller": "^3.0.0",

@@ -23,0 +23,0 @@ "debug": "^4.3.4",

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

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

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

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

Sorry, the diff of this file is not supported yet

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