Question/Best Practice: How would you handle this?

[telegraf]

Question/Best Practice: How would you handle this?

[dotcypress]

Hey Zwe!

Thank you for feedback. Much appreciated.

Approach with registration callback_query handlers "on the fly" isn't ok. For example, graceful restart is't possible with in-memory handlers.

Related to your problem: you might use db for storing 'authorization' task details.

app.action('enable', startEnableHandler)

function startEmailHandler(ctx) {
  // if (!this.session.started) return; // BTW: You can filter this on top level ;)
  // const email
  // delete this.session.started;
  // messageId = sendMessage(adminId, "Hey, ${email} wants to be enabled, is it ok?", keyboardWithYesAndNo);
  // db.save(messageId, { user, email, etc })
}

function startEnableHandler(ctx) {
  // data = db.get(ctx.message.id)  
  // const userId = data...
  // const telegramId = data...
  // user.telegramId = telegramId;
  // sendMessage(telegramId, "You are enabled");
  // sendMessage(adminId, "Done");
}

This library is inspired by koa and the main feature of Telegraf is middleware/cascading. Now you can build powerful bots from tiny blocks. Check out Telegraf middlewares for examples.

I recommend you read samples from telegraf-flow, it's experimental middleware for complex chatbots. We use 'scene' abstraction for handling user conversation flow and structure of our bots stays simple.

[Zweer]

Hey,

thanks, the "messageId" idea is really good, haven't thought about it!!!
In this way it a much more clean!!!

Good idea the Flow lib, I'm gonna have a look!!!

Thanks a lot!