From d43119770b56b1b7696f515a5f2fe0c064ff3393 Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Thu, 23 Mar 2023 20:08:23 +0000 Subject: [PATCH] Update content of files --- .../web/corefork.telegram.org/api/errors.html | 2 +- data/web/corefork.telegram.org/api/links.html | 64 +++++++++++++++++-- .../d0a8b6d650be9812c3.html | 1 + .../de2c1dc08a54bde597.html | 1 - 4 files changed, 62 insertions(+), 6 deletions(-) create mode 100644 data/web/corefork.telegram.org/file/464001078/11894/771BiZG9OeI.94769.json/d0a8b6d650be9812c3.html delete mode 100644 data/web/corefork.telegram.org/file/464001173/109f8/k9gTkjfzNHs.87735.json/de2c1dc08a54bde597.html diff --git a/data/web/corefork.telegram.org/api/errors.html b/data/web/corefork.telegram.org/api/errors.html index fc18c5174b..da794cfacc 100644 --- a/data/web/corefork.telegram.org/api/errors.html +++ b/data/web/corefork.telegram.org/api/errors.html @@ -49,7 +49,7 @@ An error is characterized by several parameters:

Error Type

A string literal in the form of /[A-Z_0-9]+/, which summarizes the problem. For example, AUTH_KEY_UNREGISTERED. This is an optional parameter.

Error Database

-

A full machine-readable JSON list of RPC errors that can be returned by all methods in the API can be found here », what follows is a description of its fields:

+

A full machine-readable JSON list of RPC errors that can be returned by all methods in the API can be found here », what follows is a description of its fields: