Daniil Gentili
e4a326e552
* refactor * Apply fixes from StyleCI * Implement https and http transport, add support for new req_pq_multi, send pending acks and objects in containers along with the next method call, remove dependency on the socket extension. * Apply fixes from StyleCI * Make types with empty constructors optional, fix phar archives (fixes #217) * Apply fixes from StyleCI * Update to layer 75 * Update github pages gemfile.lock
1.9 KiB
1.9 KiB
| title | description |
|---|---|
| user | Represents user |
Constructor: user
Represents user
Attributes:
| Name | Type | Required | Description |
|---|---|---|---|
| id | int | Yes | User identifier |
| first_name | string | Yes | User first name |
| last_name | string | Yes | User last name |
| username | string | Yes | User username |
| phone_number | string | Yes | User's phone number |
| status | UserStatus | Optional | User's online status |
| profile_photo | profilePhoto | Yes | User profile photo, nullable |
| my_link | LinkState | Yes | Relationships from me to other user |
| foreign_link | LinkState | Yes | Relationships from other user to me |
| is_verified | Bool | Yes | True, if user is verified |
| restriction_reason | string | Yes | If non-empty, contains the reason, why access to this user must be restricted. Format of the string is "{type}: {description}". -{type} contains type of the restriction and at least one of the suffixes "-all", "-ios", "-android", "-wp", which describes platforms on which access should be restricted. For example, "terms-ios-android". {description} contains human-readable description of the restriction, which can be showed to the user |
| have_access | Bool | Yes | If false, the user is inaccessible and the only known information about it is inside this class. It can't be passed to any method except GetUser. Currently it can be false only for inaccessible authors of the channel posts |
| type | UserType | Yes | Type of the user |
| language_code | string | Yes | Bots only. IETF language tag of users language |