andreacavalli/tdlib-fork
Archived
1
0
Fork 0
Code Pull Requests Releases Activity

Add a comma,

Browse Source 
GitOrigin-RevId: 37194c038eb13d2e6246ffb374dc3cea4c14478e
This commit is contained in:
levlam 2020-01-31 03:47:28 +03:00
parent 1313fb1543
commit 4f7763f6fb
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
td/telegram/td_json_client.h
View File

@ -15,7 +15,7 @@
* The JSON serialization of TDLib API objects is straightforward: all API objects are represented as JSON objects with * The JSON serialization of TDLib API objects is straightforward: all API objects are represented as JSON objects with
* the same keys as the API object field names. The object type name is stored in the special field '@type' which is * the same keys as the API object field names. The object type name is stored in the special field '@type' which is
* optional in places where type is uniquely determined by the context. * optional in places where type is uniquely determined by the context.
* Fields of Bool type are stored as Boolean, fields of int32, int53 and double types are stored as Number, fields of * Fields of Bool type are stored as Boolean, fields of int32, int53, and double types are stored as Number, fields of
* int64 and string types are stored as String, fields of bytes type are base64 encoded and then stored as String, * int64 and string types are stored as String, fields of bytes type are base64 encoded and then stored as String,
* fields of vector type are stored as Array. * fields of vector type are stored as Array.
* The main TDLib interface is asynchronous. To match requests with a corresponding response a field "@extra" can * The main TDLib interface is asynchronous. To match requests with a corresponding response a field "@extra" can