Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Defaults.business_connection_id #4193

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

Open
Bibo-Joshi opened this issue Apr 7, 2024 · 0 comments
Open

Defaults.business_connection_id #4193

Bibo-Joshi opened this issue Apr 7, 2024 · 0 comments

Comments

@Bibo-Joshi
Copy link
Member

What kind of feature are you missing? Where do you notice a shortcoming of PTB?

Bot API 7.2 added the parameter business_connection_id to all the send_* methods.
I imagine that if a business wants to connect a bot to its business account, that often times it will have a custom-build bot for that such that the bot will only ever see one fixed business connection. Moreover, the bot would only ever do communication via the business connection.
For such use cases it would be benefitial if one could set a default value for the business_connection_id parameter via PTBs Defaults mechanism.

Describe the solution you'd like

Add Defaults.business_connection_id and make the necessary adaptions in ExtBot code.

Describe alternatives you've considered

If Message.reply_* already passes business_connection_id as discussed in #4180 (comment), that may already cover many of the use cases. So Defaults.business_connection_id might not be completely crucial.

Additional context

I would see this as minor priority (+0), especially since the functionality is very new and we don't know yet how many people will actually be using this. If someone would like to PR for this, they are welcome to, but I personally wouldn't put any effort into this from the PTB team in the forseeable future.

@Bibo-Joshi Bibo-Joshi changed the title [FEATURE] Defaults.business_connection_id Defaults.business_connection_id Nov 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant