added ctx.menu.at function

[zxsleebu]

useful function for custom methods.
i don't actually have a deno environment, so you should necessarily test this pr!

[KnorpelSenf]

Will review it tonight. You can test your changes by running

npm install github:zxsleebu/menu

[KnorpelSenf]

In fact, you can compile it simply by running npm i. No Deno needed.

[KnorpelSenf]

This is a breaking change.

[KnorpelSenf]

These changes make ctx.menu.at only available inside button handlers. Was that intended?

#14 outlines that menus should be accessible everywhere, so you can for example do this:

bot.command("menu", ctx => ctx.reply("Menu:", {
  // Send 'my-menu'
  reply_markup: ctx.menu.at("my-menu")
}))

Your changes do not permit that.

[zxsleebu]

These changes make ctx.menu.at only available inside button handlers. Was that intended?

#14 outlines that menus should be accessible everywhere, so you can for example do this:

bot.command("menu", ctx => ctx.reply("Menu:", {
  // Send 'my-menu'
  reply_markup: ctx.menu.at("my-menu")
}))

Your changes do not permit that.

yes, that was fully intended.
i was trying to make a wrapper for menus which allows them to have preset text content.
i though this change is the simpliest thing to at least minimally simplify custom menu management.
i ended up making a custom patch, but i also agree that ctx.menu.at should exist and be global.
here's an example of my code. maybe you will like the idea of menus with preset text.

const devSettingsMenu = new AutoMenu("devSettingsMenu", async (ctx, menu) => {
    await ctx.reply(`Developer settings`, { reply_markup: menu });
}).text("Request API-Key", ctx => ctx.reply('API-Key requested successfuly'))
    .fastBack()

[KnorpelSenf]

I neither understand your use case nor the code snippet and I'm also not sure if they have anything to do with each other

[KnorpelSenf]

Is that like a side-effect function that runs when the menu is sent somewhere? So you end up sending two menus? Or how else would you send a menu now?