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
Months ago i opened an issue regarding the event handler not being invoked, that issue was half fixed but it was related to the fact that usePusher sometimes do not re-bind (when the component/dependencies re-render or its just simply not registered on pusher.js)
What I would suggest is having a warning/error from usePusher when a pusher event is consumed on the client-side (via ws) but there are no handlers for it OR its simply not registered and it would help a lot debugging
This feature could be enabled in dev only or via some kind of debugging flag and would help a lot in identifying some issues
The text was updated successfully, but these errors were encountered:
I have a simple workaround for this, i have a middleware on Pusher.log method and i simply check if the message type includes callback not handled but its not so perfect, i think we can close this issue because you would end up doing the same or something similiar, sorry for the noise but i can share my implementation if you want
Months ago i opened an issue regarding the event handler not being invoked, that issue was half fixed but it was related to the fact that usePusher sometimes do not re-bind (when the component/dependencies re-render or its just simply not registered on pusher.js)
What I would suggest is having a warning/error from usePusher when a pusher event is consumed on the client-side (via ws) but there are no handlers for it OR its simply not registered and it would help a lot debugging
This feature could be enabled in dev only or via some kind of debugging flag and would help a lot in identifying some issues
The text was updated successfully, but these errors were encountered: