From 7b9b1fc36a2f869e3eb203e8eb49a7767b86330a Mon Sep 17 00:00:00 2001 From: delthas Date: Fri, 16 Dec 2022 11:46:02 +0100 Subject: Fix processing CHATHISTORY TAGMSG as standalone messages Receiving a TAGMSG in chathistory causes the handler to return nil. Previously this caused the handler to be called again without the playblack flag, causing us to emit events out of their history context. This meant we would show typing notifications for users from chathistory batches. Soju will soon be able to send TAGMSG messages in its chathistory, so we're fixing that now. --- irc/session.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/irc/session.go b/irc/session.go index 04942ae..0e0d6ba 100644 --- a/irc/session.go +++ b/irc/session.go @@ -655,8 +655,8 @@ func (s *Session) handleRegistered(msg Message) (Event, error) { Target: b.Target, Messages: append(b.Messages, ev), } - return nil, nil } + return nil, nil } } return s.handleMessageRegistered(msg, false) -- cgit v1.2.3