We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently interactions with bot done via this scheme: user needs to send message with this layout: <command> <data>
<command> <data>
Telegram interface suggests autocompletion for commands, however current design doesn't allow to combine autocompletion with additional data.
Either use commands as state changers, e. g.:
Or, don't use commands at all, instead:
Both options will make backend more complex, bur will increase convenience for end user.
Whether such trade off is worth it/applicable/desirable is up to you.
I appreciate the functionality in any case. Thank you!
The text was updated successfully, but these errors were encountered:
It's good proposal, I'll think about this. Thank you!
Sorry, something went wrong.
kiriharu
No branches or pull requests
Problem
Currently interactions with bot done via this scheme: user needs to send message with this layout:
<command> <data>
Telegram interface suggests autocompletion for commands, however current design doesn't allow to combine autocompletion with additional data.
Proposal
Either use commands as state changers, e. g.:
Or, don't use commands at all, instead:
Both options will make backend more complex, bur will increase convenience for end user.
Whether such trade off is worth it/applicable/desirable is up to you.
I appreciate the functionality in any case. Thank you!
The text was updated successfully, but these errors were encountered: