pch/picoclaw
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Merge pull request #3135 from ZOOWH/fix/3110-telegram-forum-thread-id

Browse source 
fix(telegram): use compositeChatID in InboundContext.ChatID for forum topics
This commit is contained in:
Mauro 2026-06-16 22:06:31 +02:00 committed by GitHub
commit 86221d470b
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 4 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
pkg/channels/telegram/telegram.go
View file

@ -1185,7 +1185,7 @@ func (c *TelegramChannel) handleMessages(ctx context.Context, messages []*telego
inboundCtx := bus.InboundContext{
Channel: c.Name(),
ChatID: fmt.Sprintf("%d", chatID),
ChatID: compositeChatID,
ChatType: peerKind,
SenderID: platformID,
MessageID: messageID,

5
pkg/channels/telegram/telegram_test.go
View file

@ -1212,8 +1212,9 @@ func TestHandleMessage_ForumTopic_SetsMetadata(t *testing.T) {
inbound, ok := <-messageBus.InboundChan()
require.True(t, ok, "expected inbound message")
// ChatID remains the parent chat; TopicID isolates the sub-conversation.
assert.Equal(t, "-1001234567890", inbound.ChatID)
// ChatID includes the thread ID for forum topics so outbound
// delivery resolves the correct topic without relying solely on TopicID fallback.
assert.Equal(t, "-1001234567890/42", inbound.ChatID)
assert.Equal(t, "group", inbound.Context.ChatType)
assert.Equal(t, "42", inbound.Context.TopicID)
}