User (user and/or userFull) information was updated.
This update can only be received through getDifference or in updates/updatesCombined constructors, so it will always come bundled with the updated user, that should be applied as usual », without re-fetching the info manually.
However, full peer information will not come bundled in updates, so the full peer cache (userFull) must be invalidated for user_id when receiving this update.
updateUser#20529438 user_id:long = Update;| Name | Type | Description |
|---|---|---|
| user_id | long | User ID |
Indicates info about a certain user.
Unless specified otherwise, when updating the local peer database, all fields from the newly received constructor take priority over the old constructor cached locally (including by removing fields that aren't set in the new constructor).
See here » for an implementation of the logic to use when updating the local user peer database.
Extended user info
When updating the local peer database », all fields from the newly received constructor take priority over the old constructor cached locally (including by removing fields that aren't set in the new constructor).
Full constructor of updates
Constructor for a group of updates.
Many constructors in the API need to be stored in a local database upon reception and should only ever be updated reactively (passively) when received via updates or by other means (as specified in the documentation), to avoid overloading the server by continuously requesting changes for the same unchanged information.