Accessing event name in callback

[andrew-aladev]

['event1', 'event2']
.forEach(function (event) {
  socket.data(event, data.bind(self, event));
})

But what about generic event names? It is not possible to predict event. We've found a way in examples:

outbound.data(['drink', '*'], function () {
  console.log('I can mix a', this.event[2], 'drink');
});

There is no information about this.event in docs. This is very important, please fix.

[andrew-aladev]

BTW What is the reason of having socket.event = [ 'data', 'present' ]? This is done by EventEmitter2. What socket want to do with event? This is the awful workaround.

[nucleardreamer]

It would probably be helpful to add some information to the readme about this.event in the EE callback, but nssocket is not particularly concerned with what you do with the data after it gets fired. The reason that exists in the EventEmitter2 scope is specifically for wildcards.

On your second comment, I have no idea what you mean. Could you provide clarity of what is a workaround?

[andrew-aladev]

@nucleardreamer, See here. I am sure that some programmer passed this.event as temporaly workaround but community decided this to be a "pattern". This is funny. Please do not use this part of "pattern".

socket.event means the last event name on the socket. Any setImmediate (for example Promise) will make socket.event meaningless for current event handler.

socket.data(['iam', 'here'], function (data) {});

You want to provide data as 1-st argument. Why second argument couldn't be a event?