From 385428dd7ed53dd1aebfed285f7069d9901a12f1 Mon Sep 17 00:00:00 2001
From: GitHub Action
Date: Sat, 15 Apr 2023 16:21:16 +0000
Subject: [PATCH] Update content of files
---
data/web/corefork.telegram.org/api/errors.html | 2 +-
data/web/corefork.telegram.org/api/layers.html | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/data/web/corefork.telegram.org/api/errors.html b/data/web/corefork.telegram.org/api/errors.html
index da794cfacc..9bffffe394 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:
errors
- All error messages and codes for each method (object).
- Keys: Error codes as strings (numeric strings)
diff --git a/data/web/corefork.telegram.org/api/layers.html b/data/web/corefork.telegram.org/api/layers.html
index d2786206c3..bcb221c4e4 100644
--- a/data/web/corefork.telegram.org/api/layers.html
+++ b/data/web/corefork.telegram.org/api/layers.html
@@ -47,6 +47,7 @@
Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.
Reaction dates.
+The RPC error database » was also updated.
Schema changes
Changed Constructors