Chaining Message Sending Properly

[telegraf]

Chaining Message Sending Properly

[dotcypress]

Hey.

Yes, ES7's async/await will help you with a charm 😉

Otherwise, you might use any approaches to call Promise chain sequentially.

Your second example is absolutely correct, you might minimize code, like following:

bot.command('start', (ctx) => ctx.replyWithHTML("Hello")
  .then(() => ctx.replyWithHTML("This"))
  .then(() => ctx.replyWithHTML("Should"))
  .then(() => ctx.replyWithHTML("Send"))
  .then(() => ctx.replyWithHTML("Sequentially"))
  .then(() => ctx.replyWithHTML("This"))
)

PS: But this is not guarantee that messages arrive to user sequentially, it's really depends on Telegram servers logic.

[joshuaquek]

Dear dotcypress,

Thank you for extremely speedy reply!

Just to check, the syntax of

bot.command('start', (ctx) => ctx.replyWithHTML("Hello")
  .then(() => ctx.replyWithHTML("One"))
  .then(() => ctx.replyWithHTML("Two"))
)

be the same as

bot.command('start', (ctx) => ctx.replyWithHTML("Hello")
  .then(() => {
      return ctx.replyWithHTML("One")
  }).then(()=>{
      return ctx.replyWithHTML("Two")
  })
)

or would it be the same as

bot.command('start', (ctx) => ctx.replyWithHTML("Hello")
  .then(() => {
      ctx.replyWithHTML("One")
  }).then(()=>{
      ctx.replyWithHTML("Two")
  })
)

Does putting the return keyword make a difference?

Hope to hear from you soon!

[dotcypress]

Hey 😃

We massively use Promises in Telegraf, and when you omit return keywork in last example - you just break Promise chain, and you will have similar result as in following example:

bot.command('start', (ctx) => {
  ctx.replyWithHTML("Hello")
  ctx.replyWithHTML("One")
  ctx.replyWithHTML("Two")
})

As you see, you lose all Promise benefits here. 😉

[dotcypress]

@joshuaquek btw, good article about asynchronous js.

[joshuaquek]

Dear dotcypress,

ok, thank you!!! (:

Your answers have been super helpful!