Hi There,
quick headsup, I was going through the documentation codebase and found this typo in the websocket node --> 'erro' should be 'error' I would assume ....
Cheers!
Edit: here too? or is the event really 'erro' .... hm 
I think it is intentional - although not necessarily how I'd chose to do it. It emits a custom error event, but it can't call it error as that's an existing event - so it calls it erro ...
Having a look at the entire commit, it does emit an erro - considering the other two opened and closed, perhaps errored would have been a better choice 
I assumed that it was capturing native events and not self generated ones - mea culpa!
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
