fix(telegram): ensure proper bot API base#557
Merged
douglas-reid merged 2 commits intomainfrom Sep 26, 2023
Merged
Conversation
douglas-reid
force-pushed
the
doug/fix-transports-and-chat-history
branch
from
0313176 to
3889c6b
Compare
douglas-reid
force-pushed
the
doug/fix-transports-and-chat-history
branch
from
3889c6b to
1d85c35
Compare
dkolas
approved these changes
Sep 26, 2023
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I think that in the refactor in 05a8f0e the behavior of the base API for Telegram became to use a
/in betweenbotand the supplied token.Per https://core.telegram.org/bots/api#making-requests, the API base should be:
https://api.telegram.org/bot<token>/METHOD_NAMENote the lack of
/betweenbotand<token>