Open GochoMugo opened 7 years ago
bump
Cannot find module 'forms-telegram' how can i resolve it?
@FaRzad-845 It's just at theory. Work is in progress to make it a reality! 😃
@kamikazechaser
what can we do now days ?
when i use two bot.on .... like this i run into trouble .... ` bot.on('message', function (msg) { var chatId = msg.chat.id; var text ="write your comment"; bot.sendMessage(chatId, text);
bot.on('message', function (msg) { var chatId = msg.chat.id; var text = "thanks for your comment"; bot.sendMessage(chatId, text); }); }); `
do you have any idea for two bot.on listener toghether?
Possibly use async await.
@kamikazechaser Excuse me ... Can you give me a example of this ... ( Async await and two or three bot.on method ) my node version is 6.9
Where the state is supposed to be stored? Memory?
We shall allow multiple stores to be used. Think of it the same way express-session works, with multiple pluggable session stores. We will probably provide a memory store by default, but they will all share the same interface.
I have worked on a PoC for the query engine. Please proceed to https://github.com/forfuturellc/mau for more information. In particular, see the example provided and see how it would work with your bot code!
Forms can allow a more complex chain of queries between the bot and the user, without requiring the programmer to define explicitly the interactions between them.
The original inspiration for this feature was from https://dev.albertocoscia.me/nodeogram/quickstart.html#forms.
While it is possible to implement this entirely in tgfancy, I believe it will be better to have a more generic solution, i.e. a form engine, that can be used across multiple platforms, other than just Telegram, using "adapters'.
A favorable API can be adapted from Inquirer.js.
The expected code would look something like: (this is hypothetical!)
tgfancy would offer a formset by default, for more implicit solutions!