FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

refactor: add enum constants by lemontree210 · Pull Request #3336 · python-telegram-bot/python-telegram-bot · GitHub

refactor: add enum constants - #3336

Closed
lemontree210 wants to merge 8 commits into
python-telegram-bot:masterfrom
lemontree210:enums-instead-of-literals-3107
Closed

refactor: add enum constants#3336
lemontree210 wants to merge 8 commits into
python-telegram-bot:masterfrom
lemontree210:enums-instead-of-literals-3107

Conversation

lemontree210 commented Nov 5, 2022
edited
Loading

Copy link
Copy Markdown
Member

addresses #3107

* add constants for `max_connections`

* expand docstring for `secret_token`
lemontree210 changed the title refactor(Bot) add enum constants for Bot.set_webhook() refactor(Bot) add enum constants Nov 5, 2022
lemontree210 changed the title refactor(Bot) add enum constants refactor: add enum constants Nov 5, 2022
harshil21 added the ⚙️ documentation affected functionality: documentation label Nov 5, 2022
* add limits for heading

* add minimum proximity_alert_radius
(as it is non-zero)

* fix docstrings that link to HEADING
constant twice instead of PROXIMITY_ALERT_RADIUS
(and hence 360 was displayed instead of 100000)
Comment thread telegram/constants.py Outdated

Copy link
Copy Markdown
Member Author

Question regarding limits for Location and send_location: I know that in Telegram API itself most limits are only listed in sendLocation and not in Location, e.g. live_period and heading.

Should I list all the limits in Location as well or do I stick to what's listed or not listed in Telegram API?

Copy link
Copy Markdown
Member

Should I list all the limits in Location as well or do I stick to what's listed or not listed in Telegram API?

I think we should stick to TG API docs.

Comment thread telegram/constants.py
lemontree210 mentioned this pull request Nov 8, 2022
8 tasks
lemontree210 added a commit that referenced this pull request Nov 8, 2022
as suggested in review for PR #3336,
but in singular (rather than `...Limits`)
to conform with review for #3343

Copy link
Copy Markdown
Member Author

closing this PR, all work moved to #3351 (with branches within same repo as opposed to fork)

github-actions Bot locked and limited conversation to collaborators Nov 15, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

⚙️ documentation affected functionality: documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants


Back | FazBrowse Home | New Git URL