You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sorry @victorperin, but I had to remove all timeout functionality because if the message is queued, it may cause the timeout for the confirmation event to expire even though the message has yet to be sent.
I did however replace the resolveOnEvent with p-event that supports timeouts. I am thinking about adding and optional options?: { timeout?: number } parameter to all Chat methods that send messages, such as Chat#join and Chat#say, so you can pass a timeout to p-event and timeout methods if needed.
Let me know what you think.
The text was updated successfully, but these errors were encountered:
Sorry @victorperin, but I had to remove all timeout functionality because if the message is queued, it may cause the timeout for the confirmation event to expire even though the message has yet to be sent.
I did however replace the
resolveOnEvent
withp-event
that supports timeouts. I am thinking about adding and optionaloptions?: { timeout?: number }
parameter to allChat
methods that send messages, such asChat#join
andChat#say
, so you can pass a timeout top-event
and timeout methods if needed.Let me know what you think.
The text was updated successfully, but these errors were encountered: