-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add fanciness: forms #5
Comments
bump |
Cannot find module 'forms-telegram' |
@FaRzad-845 It's just at theory. Work is in progress to make it a reality! 😃 |
what can we do now days ? when i use two bot.on .... bot.on('message', function (msg) { do you have any idea for two bot.on listener toghether? |
Possibly use async await. |
@kamikazechaser |
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! |
I have recently published a package I personally use for managing the context of the dialog between the user and the bot. You can find it here, maybe with a little modification it could be useful here as well. |
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!
The text was updated successfully, but these errors were encountered: