fix: wrong match keyword causing disconnects on typing event
This commit is contained in:
@@ -291,7 +291,7 @@ async fn worker(
|
|||||||
match payload {
|
match payload {
|
||||||
ClientMessage::BeginTyping { channel } => {
|
ClientMessage::BeginTyping { channel } => {
|
||||||
if !subscribed.read().await.contains(&channel) {
|
if !subscribed.read().await.contains(&channel) {
|
||||||
break;
|
continue;
|
||||||
}
|
}
|
||||||
|
|
||||||
EventV1::ChannelStartTyping {
|
EventV1::ChannelStartTyping {
|
||||||
@@ -303,7 +303,7 @@ async fn worker(
|
|||||||
}
|
}
|
||||||
ClientMessage::EndTyping { channel } => {
|
ClientMessage::EndTyping { channel } => {
|
||||||
if !subscribed.read().await.contains(&channel) {
|
if !subscribed.read().await.contains(&channel) {
|
||||||
break;
|
continue;
|
||||||
}
|
}
|
||||||
|
|
||||||
EventV1::ChannelStopTyping {
|
EventV1::ChannelStopTyping {
|
||||||
|
|||||||
Reference in New Issue
Block a user