From 0b009f21a8a2b4231ac4dd15b5ebb79282b0fdf7 Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Sun, 30 Jan 2022 10:43:28 +0000 Subject: [PATCH] Update content of files --- .../decryptedMessageActionNotifyLayer.html | 151 ++++++++++++++++++ 1 file changed, 151 insertions(+) create mode 100644 data/core.telegram.org/constructor/decryptedMessageActionNotifyLayer.html diff --git a/data/core.telegram.org/constructor/decryptedMessageActionNotifyLayer.html b/data/core.telegram.org/constructor/decryptedMessageActionNotifyLayer.html new file mode 100644 index 0000000000..23af64d198 --- /dev/null +++ b/data/core.telegram.org/constructor/decryptedMessageActionNotifyLayer.html @@ -0,0 +1,151 @@ + + + + + decryptedMessageActionNotifyLayer + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageActionNotifyLayer

+ +

A notification stating the API layer that is used by the client. You should use your current layer and take notice of the layer used on the other side of a conversation when sending messages.

+

+ +
+
===17===
+decryptedMessageActionNotifyLayer#f3048883 layer:int = DecryptedMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
layerintLayer number, must be 17 or higher (this contructor was introduced in Layer 17).
+

Type

+

DecryptedMessageAction

+

Related pages

+

Layers

+

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

+ +
+ +
+
+ +
+ + + + + +