Add official telegram test environment support #1320
Conversation
This file contains 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
https://core.telegram.org/bots/webapps **** Using bots in the test environment To log in to the test environment, use either of the following: iOS: tap 10 times on the Settings icon > Accounts > Login to another account > Test. Telegram Desktop: open ☰ Settings > Shift + Alt + Right click ‘Add Account’ and select ‘Test Server’. macOS: click the Settings icon 10 times to open the Debug Menu, ⌘ + click ‘Add Account’ and log in via phone number. The test environment is completely separate from the main environment, so you will need to create a new user account and a new bot with @Botfather. After receiving your bot token, you can send requests to the Bot API in this format: https://api.telegram.org/bot<token>/test/METHOD_NAME Note: When working with the test environment, you may use HTTP links without TLS to test your Web App. *****
A semicolon were missing in the Standalone reply code. The reply signature changed and needs a BiConsumer<BaseAbilityBot, Update> instead of Consumer<Update> in the Ability reply
Add getMessageId to MaybeInaccessibleMessage According to https://core.telegram.org/bots/api#maybeinaccessiblemessage
…ed from 'Boolean' to 'String' (according to TelegramBotAPI Official Documentation). (rubenlagus#1315)
* fix force=true for WriteAccessAllowed * + test and fixtures on write access allowed
* Fix path for GetMyName method * Add missing sticker methods from API 6.6 * Fix possible NPE in InputSticker validation * Add ReplyParameters to SendInvoice API method * Removed mysterious fields in SetChatTitle
rubenlagus
force-pushed
the
dev
branch
2 times, most recently
from
c4394aa
to
7df1524
Compare
rubenlagus
force-pushed
the
dev
branch
4 times, most recently
from
bc4fd52
to
65c33e0
Compare
4repaXXX
reviewed
Jun 23, 2024
| @@ -279,6 +279,14 @@ private List<Update> getUpdatesFromServer() throws IOException { | |||
| } | |||
| } | |||
|
|
|||
| private String getApiUrl() { | |||
There was a problem hiding this comment.
Why we need this method? It look like duplication of logic with getBaseUrl()
| @@ -123,7 +120,11 @@ public final DefaultBotOptions getOptions() { | |||
| } | |||
|
|
|||
| public String getBaseUrl() { | |||
| return options.getBaseUrl() + getBotToken() + "/"; | |||
| String baseUrl = options.getBaseUrl() + getBotToken() + "/"; | |||
There was a problem hiding this comment.
Does not it better to allow user set url for http request on start? For example, using standard setBaseUrl, and just use everywhere method getBaseUrl(). And don't add implicit changes. What if in future telegram decide to change url again.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add "/test/" into telegram api url for test environments.
From the docs:
https://core.telegram.org/bots/webapps
Using bots in the test environment
To log in to the test environment, use either of the following:
iOS: tap 10 times on the Settings icon > Accounts > Login to another account > Test.
Telegram Desktop: open ☰ Settings > Shift + Alt + Right click ‘Add Account’ and select ‘Test Server’.
macOS: click the Settings icon 10 times to open the Debug Menu, ⌘ + click ‘Add Account’ and log in via phone number.
The test environment is completely separate from the main environment, so you will need to create a new user account and a new bot with @Botfather.
After receiving your bot token, you can send requests to the Bot API in this format:
https://api.telegram.org/bot/test/METHOD_NAME
Note: When working with the test environment, you may use HTTP links without TLS to test your Web App. *****