update.From when it came from unknown source (CallbackQuery/Message)

[BeyCoder]

Problem

Sometimes, update.Message.From or update.Message.Chat could be nil if it's CallbackQuery update. So, I always need to repeat the same if statement. Example:

var userId int64
var chatId int64
if update.CallbackQuery != nil {
	userId = update.CallbackQuery.From.ID
	chatId = update.CallbackQuery.Message.Message.Chat.ID
} else {
	userId = update.Message.From.ID
	chatId = update.Message.Chat.ID
}

Solution

Add the methods FromUser() and FromChat() to models.Update

Conclusion

It will help to easily retrieve the ChatID or UserID from the update. If necessary, I can contribute and send a PR to fix this issue so you can assign me.

[negasus]

There is no From field in the Update model.
Your example will fire panic if Update for example has only InlineQuery field.

If you handle Update in default handler, you should manually check nil fields.

But you can use bot.WithCallbackQueryDataHandler. See example https://github.com/go-telegram/bot/blob/main/examples/inline_keyboard/main.go#L20C3-L20C35

[BeyCoder]

There is no From field in the Update model.

My typo, sorry: update.From -> update.Message.From

Your example will fire panic if Update for example has only InlineQuery field.

Because of that, I suggest creating the methods update.FromChat() and update.FromUser(), so instead of writing:

var userId int64
var chatId int64
if update.CallbackQuery != nil {
	userId = update.CallbackQuery.From.ID
	chatId = update.CallbackQuery.Message.Message.Chat.ID
} else if update.InlineQuery != nil {
...
} else if ...  { // for example BusinessMessage or others
...
} else if ... {
	userId = update.Message.From.ID
	chatId = update.Message.Chat.ID
}

We can write:

userId := update.FromUser()
chatId := update.FromChat()
if chatId != nil {
// action
}

[BeyCoder]

But you can use bot.WithCallbackQueryDataHandler. See example https://github.com/go-telegram/bot/blob/main/examples/inline_keyboard/main.go#L20C3-L20C35

I have a hybrid handler that uses both update.CallbackQuery and update.Message and has the same logic

[BeyCoder]

@negasus , could you please check my PR?