-
-
Notifications
You must be signed in to change notification settings - Fork 187
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
How to start conversation like botkit #65
Comments
There's no built-in support for conversations in slack-ruby-bot. That would require storage for one. Labeling as a feature request. |
This would be such a cool feature! I had to implement conversations with a bot a while back and it was a bit of a pain. Any thoughts around storage options? By default, botkit just uses JSON files on the filesystem but gives you the option to include your own storage module |
Something pluggable would be nice. Also check out slack-ruby/slack-ruby-bot-server#3. |
We used redis for a simple data storage implementation with slack-ruby-bot. Our use case was a bot that lets multiple Slack users post questions using a "question" command, with a "list" command that lists all of the posted questions. |
I was thinking to open a similar issue. What I have in my mind is replicating AWS lex framework and turn slack ruby bot into a similar framework. I like the way AWS Lex works and I think we should adopt a similar behavior on top of the current codebase (no NLP yet). @dblock what do you think? |
I am open to this, however I think what we're all saying is that we want multiple DSLs on top of similar infrastructure. Some people want a command DSL, some people want object inheritance and others a Q&A. I think we should go into a direction where that's all possible and one day each even lives in a separate gem. |
Thanks for a nice gem!
Like ask on botkit, How can I send Yes/No prompt message?
The text was updated successfully, but these errors were encountered: