-
-
Notifications
You must be signed in to change notification settings - Fork 797
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
Pretty work with state #1388
Comments
Just look at the Scenes documentation: https://docs.aiogram.dev/en/dev-3.x/dispatcher/finite_state_machine/scene.html We already have simplified mechanism to work with states - Scenes. |
Oh, i see "alternative" section in your message, i dont think so this is a god idea (from the architecture side) |
Yes, this may not be the best idea from the point of view of the architecture of the framework, but from the point of view of usability, there are many conveniences in this. |
Of course! You can do whatever you want and create pull requests to this repository, useful ideas can be merged into library Welcome to open-source project :D |
aiogram version
3.x
Problem
I've been writing telegram bots on aiogram for quite some time.
I like everything, but I don’t really like working with states. You have to write a lot of typical code.
You must describe the state model, and then write handlers for each item.
I believe that this can be implemented a little more convenient for developers
Possible solution
I believe that it is possible to write a wrapper over the existing state system that can process a state in one line
Alternatives
I know about state scenes in 3.x, but I want something a little different
Code example
Additional information
If I'm wrong on some issues, please correct me, this is my first micro contribution to open source, sorry if something is wrong
The text was updated successfully, but these errors were encountered: