From aff89515e1ece174a7eb4d8413b97f04acd140e9 Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Sat, 15 Apr 2023 13:48:45 +0000 Subject: [PATCH] Update content of files --- .../corefork.telegram.org/api/bots/webapps.html | 4 ++-- data/web/corefork.telegram.org/api/layers.html | 16 ++++++++-------- data/web/corefork.telegram.org/api/links.html | 8 ++++---- .../constructor/appWebViewResultUrl.html | 6 +++--- .../constructor/botApp.html | 10 +++++----- .../constructor/inputBotAppID.html | 10 +++++----- .../constructor/inputBotAppShortName.html | 8 ++++---- .../constructor/messages.botApp | 8 ++++---- .../method/messages.getBotApp | 8 ++++---- .../method/messages.requestAppWebView | 14 +++++++------- data/web/corefork.telegram.org/methods.html | 4 ++-- .../type/AppWebViewResult.html | 10 +++++----- data/web/corefork.telegram.org/type/BotApp.html | 8 ++++---- .../corefork.telegram.org/type/InputBotApp.html | 10 +++++----- .../corefork.telegram.org/type/messages.BotApp | 10 +++++----- 15 files changed, 67 insertions(+), 67 deletions(-) diff --git a/data/web/corefork.telegram.org/api/bots/webapps.html b/data/web/corefork.telegram.org/api/bots/webapps.html index 16c51d7c8e..87dd25f6ae 100644 --- a/data/web/corefork.telegram.org/api/bots/webapps.html +++ b/data/web/corefork.telegram.org/api/bots/webapps.html @@ -153,7 +153,7 @@ The webview must be closed after invoking the messages.requestWebView, and then open a webview using the url contained in the returned webViewResultUrl.

After loading the webview, until it is closed by a web_app_close event, the user client must invoke messages.prolongWebView every 60 seconds: if the method call returns QUERY_ID_INVALID, the webview must be closed.

The opened URL's fragment parameters already contain basic information about the user and a query_id parameter, that is exposed by the bot web apps JS library: this query_id can then be used by the bot to invoke messages.sendWebViewResultMessage, passing an InputBotInlineResult constructor that will automatically send a message with optionally attached media, and even inline buttons on behalf of the user.

-

Bot web apps

+

Named bot web apps

Schema:

inputBotAppID#a920bd7a id:long access_hash:long = InputBotApp;
 inputBotAppShortName#908c0407 bot_id:InputUser short_name:string = InputBotApp;
@@ -172,7 +172,7 @@ The webview must be closed after invoking the bot web app links ».  

+

Another way to open web apps is by using named bot web app links ».

These links are different from bot attachment menu deep links », because they don't require the user to install an attachment menu, and a single bot can offer multiple web apps, distinguished by their short_name.

These links should be handled as follows:

New Constructors
    -
  • Added inputBotAppID - Used to fetch information about a bot web app by its ID
  • -
  • Added inputBotAppShortName - Used to fetch information about a bot web app by its short name
  • +
  • Added inputBotAppID - Used to fetch information about a named bot web app by its ID
  • +
  • Added inputBotAppShortName - Used to fetch information about a named bot web app by its short name
  • Added botAppNotModified - Bot app info hasn't changed.
  • -
  • Added botApp - Contains information about a bot web app.
  • -
  • Added messages.botApp - Contains information about a bot web app
  • -
  • Added appWebViewResultUrl - Contains the link that must be used to open a bot web app.
  • +
  • Added botApp - Contains information about a named bot web app.
  • +
  • Added messages.botApp - Contains information about a named bot web app
  • +
  • Added appWebViewResultUrl - Contains the link that must be used to open a named bot web app.
  • Added inlineBotWebView - Specifies a bot web app button, shown on top of the inline query results list.
  • Added readParticipantDate - Contains info about when a certain participant has read a message
  • Added updateGroupInvitePrivacyForbidden - 0-N updates of this type may be returned only when invoking messages.addChatUser, channels.inviteToChannel or messages.createChat: it indicates we couldn't add a user to a chat because of their privacy settings; if required, an invite link can be shared with the user, instead.
  • diff --git a/data/web/corefork.telegram.org/api/links.html b/data/web/corefork.telegram.org/api/links.html index f57576f356..7d6999b8be 100644 --- a/data/web/corefork.telegram.org/api/links.html +++ b/data/web/corefork.telegram.org/api/links.html @@ -828,10 +828,10 @@ tg://resolve?domain=<bot_username>&startgroup&admin=<permission -

    Bot web app links

    -

    Used to share bot web apps.

    -

    These links are different from bot attachment menu deep links, because they don't require the user to install an attachment menu, and a single bot can offer multiple web apps, distinguished by their short_name.

    -

    These links should be handled as specified in the bot web app documentation ».

    +

    Named bot web app links

    +

    Used to share named bot web apps.

    +

    These links are different from bot attachment menu deep links, because they don't require the user to install an attachment menu, and a single bot can offer multiple named web apps, distinguished by their short_name.

    +

    These links should be handled as specified in the named bot web app documentation ».

    t.me syntax:

    t.me/<bot_username>/<short_name>?startapp=<start_parameter>

    tg: syntax:

    diff --git a/data/web/corefork.telegram.org/constructor/appWebViewResultUrl.html b/data/web/corefork.telegram.org/constructor/appWebViewResultUrl.html index 668202abb5..f4f2698ae5 100644 --- a/data/web/corefork.telegram.org/constructor/appWebViewResultUrl.html +++ b/data/web/corefork.telegram.org/constructor/appWebViewResultUrl.html @@ -4,10 +4,10 @@ appWebViewResultUrl - + - + @@ -42,7 +42,7 @@

    appWebViewResultUrl

    -

    Contains the link that must be used to open a bot web app.

    +

    Contains the link that must be used to open a named bot web app.