guessing no?
I'm curious what the chats and users properties of the users.UserFull object actually represent
https://tl.telethon.dev/constructors/users/user_full.html
I tried it for me, and the users list just has one User object, which is the same user as the UserFull object in full_user, and chats was empty
server sends you list of relevant chats and users for requests and Updates, it being the same user as userFull is the point. a User object has info UserFull doesn't, to avoid extra request, you get that as a gift
Ahhh, okay! What's the chats section then? Maybe shared chats or something? And why is user a list, rather than just the one... Maybe I need to poke around more
It's just for compatibility. libraries or usual Telegram apps search for .chats and .users fields in any response or Update to preload entities. User or Channel objects have access_hash crucial to be able to use id and create InputPeer also, server behavior is not defined, it can return you .chats too for any reason if it thinks you need to cache it mainly, you should never rely on .chats and .users to get peers, only to the actual fields of the response, int id or Peer or InputPeer, object can be missing or wrong order any time
Обсуждают сегодня