-
Notifications
You must be signed in to change notification settings - Fork 57
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
Possibility to pass optional arguments in step_to #172
Comments
Another benefit of this feature is more powerful and contextual messages to CatchAll system. CatchAll scheme is a awesome to retry and limit wrongs inputs of the users, but your messages are very generics, to all cases. If we could pass the error as parameter, the bot will be able to respond more efficiently and contextually. We could create validations that raise exceptions and for each exception return respective message with useful information.
And in run_catch_all we can pass the error type.
And in our
|
Perhaps #183 can work for you. |
Works fine!! Thanks @bhtabor |
Hello my friends,
Me again :P
During all that I used Stealth, has a functionality that I always missed. The possibility of passing a parameter to another flow action.
For example, when I work with dynamic items as a product listing. This would be my controller:
And this, my reply.
This is a little ugly to me and not reusable. I need copy and paste parte this code in product_details.yml and, every that this change, change in all other parte of project
A see a, maybe, better way to do this. If we could pass a product id with a params, and control this in controller, otherwise replies? Like this (is only a example to illustrate the case):
Some like this. Controller would orchestrate information and replies are only responsible for formatting them, and thus would better separation of responsibilities.
say_products.yml.erb
only this:And
say_product_details.yml.erb
only this.The text was updated successfully, but these errors were encountered: