In ruben implementation, the TLMethod is TLRequestUsersGetFullUser passing the userId. But, when I do the
RPC call, is returned the object FullUser, but the parameters in the Telegram docs:
real_first_name:string real_last_name:string
Don't come with the request response. The code I used the do this:
public void getFullUser(IUser user) {
LOG.info("RPC to get full user to user [{}]", ToStringBuilder.reflectionToString(user));
try {
TLRequestUsersGetFullUser getFullUser = new TLRequestUsersGetFullUser();
getFullUser.setId(TLFactory.createTLInputUser(user));
TLUserFull userFull = kernelComm.doRpcCallSync(getFullUser);
if (userFull.getUser() instanceof TLUser) {
LOG.info("USER_FULL: [{}]", ToStringBuilder.reflectionToString(userFull));
LOG.info("USER: [{}]", ToStringBuilder.reflectionToString(userFull.getUser()));
}
} catch (Exception ex) {
LOG.error("Exception getting user info", ex);
}
}
Exists a method for this in the official documentation, https://core.telegram.org/method/users.getFullUser.
In ruben implementation, the TLMethod is TLRequestUsersGetFullUser passing the userId. But, when I do the RPC call, is returned the object FullUser, but the parameters in the Telegram docs:
Don't come with the request response. The code I used the do this:
The LOG returns this:
There is another way to get this info? Or change the ruben API and make a pr?