-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
new: add register_next_step_handler for asyncbot #2344
new: add register_next_step_handler for asyncbot #2344
Conversation
No |
why? |
|
It is based on your recommendation that suggest to use state It is really useful to have steps in async The step in sync is buggy also. It does not process middlewares. |
Steps are an old, somewhat "deprecated"(though not yet and won't probably), so there's no point of improving them when there's a solution(states) which I am currently working on to even further improve |
the problem of state is that we can not have more complex workflow |
What do you even mean by "10 elements"? |
yes 10 inputs from the user great thanks |
@coder2020official Thanks for your great job. It would be great if we can have a timeline about your solution |
Hi, my solution never came to existence, and I haven't had enough time recently either. I wouldn't mind re opening this. I'm open to proposals, or I'll look at this issue again in December and see if there's any way I can simplify states logic. Also, I have re implemented states to make them easier to use :) |
I'll open an issue |
Thanks |
Description
create missing
register_next_step_handler in asyncbot using auto state
Describe your tests
run step_example.py in async_telebot
Python version:
OS:
Checklist: