Update documentation

Closes #1733.
This commit is contained in:
Lonami Exo 2021-03-31 10:54:18 +02:00
parent 2fbf850841
commit 5b91adf62d
2 changed files with 1 additions and 10 deletions

View File

@ -26,15 +26,6 @@ of everything you can do.
can also do ``from telethon.tl import types, functions``. Both work.
.. important::
All the examples in this documentation assume that you have
``from telethon import sync`` or ``import telethon.sync`` for the
sake of simplicity and that you understand what it does (see
:ref:`compatibility-and-convenience` for more). Simply add
either line at the beginning of your project and it will work.
You should also refer to the documentation to see what the objects
(constructors) Telegram returns look like. Every constructor inherits
from a common type, and that's the reason for this distinction.

View File

@ -155,7 +155,7 @@ INLINE_RESULT_EXPIRED,400,The inline query expired
INPUT_CONSTRUCTOR_INVALID,400,The provided constructor is invalid
INPUT_FETCH_ERROR,400,An error occurred while deserializing TL parameters
INPUT_FETCH_FAIL,400,Failed deserializing TL payload
INPUT_FILTER_INVALID,400,The search query filter is valid
INPUT_FILTER_INVALID,400,The search query filter is invalid
INPUT_LAYER_INVALID,400,The provided layer is invalid
INPUT_METHOD_INVALID,400,The invoked method does not exist anymore or has never existed
INPUT_REQUEST_TOO_LONG,400,The input request was too long. This may be a bug in the library as it can occur when serializing more bytes than it should (like appending the vector constructor code at the end of a message)

1 name codes description
155 INPUT_CONSTRUCTOR_INVALID 400 The provided constructor is invalid
156 INPUT_FETCH_ERROR 400 An error occurred while deserializing TL parameters
157 INPUT_FETCH_FAIL 400 Failed deserializing TL payload
158 INPUT_FILTER_INVALID 400 The search query filter is valid The search query filter is invalid
159 INPUT_LAYER_INVALID 400 The provided layer is invalid
160 INPUT_METHOD_INVALID 400 The invoked method does not exist anymore or has never existed
161 INPUT_REQUEST_TOO_LONG 400 The input request was too long. This may be a bug in the library as it can occur when serializing more bytes than it should (like appending the vector constructor code at the end of a message)