'Unbind' earlier set triggers (telegraf.hears)
See original GitHub issueAs far as I can see it is not possible to override or unbind earlier set telegraf.hears triggers.
For instance if the following code is executed:
app.hears('test', ({reply}) => {
return reply("FIRST!");
});
app.hears('test', ({reply}) => {
return reply("SECOND!");
});
app.hears('test', ({reply}) => {
return reply("THIRD!");
});
If the bot hears test it will always reply with “FIRST!”.
Is there any way to unbind old triggers or to override them?
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (1 by maintainers)
Top Results From Across the Web
Node Telegraf callback button - Stack Overflow
For what we need to pass data to callback button in in simple keyboard (not inline), if thats doesn't matter? Example: const mainMenuKeyboard...
Read more >Expand Kubernetes Monitoring with Telegraf Operator
Telegraf Operator then sets the configuration for the entire cluster so your users don't need to worry about configuring a metrics destination ...
Read more >Build a Telegram Bot using TypeScript, Node.js, and Telegraf ...
I am using a computer with Linux Mint 20.2 and Visual Studio Code 1.61.2 to write the bot. The project will use the...
Read more >Practical Advice for Auto Setup - GroundWork Support
Reconfiguration as desired (updating the instructions file as needed; dropping a new trigger file) when the set of services to be monitored on...
Read more >How to Add a Telegram Bot to Telegram Group (2022 Tutorial)
So the first step we need to do, is create our own Telegram group. ... in “Disable” or click on the button, you...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@NoahKr as I understood, you want some sort of
dynamic text routing
. Actually, you can use.hears
like that:@NoahKr yes.