Regresssion in PR#96 about emittery HOT 4 CLOSED

Yup. Or we can have a special function that emits the meta events on a given emitter instance. Something like this.

async function emitMetaEvent(emitter, event, data) {
  metaEventsAllowed = true
  await emitter.emit(event, data)
  metaEventsAllowed = false
}

The only benefit of this function over the callback approach is, we will not end up creating too many anonymous functions.

if (!isMetaEvent(eventName)) {
  emitMetaEvent(this, listenerAdded, {eventName, listener})
}

from emittery.

// @lukehorvat

from emittery.

Ouch. Sorry for the oversight.

I have one idea. We could have a private withMetaEventsAllowed function which would allow Emittery to run some internal code in a "privileged" way (like running sudo or whatever). All of the internal calls to emit could be wrapped in this function.

let metaEventsAllowed = false;

function withMetaEventsAllowed(callback) {
  metaEventsAllowed = true;
  callback();
  metaEventsAllowed = false;
}

So, for example, this code:

Would become this:

if (!isMetaEvent(eventName)) {
  withMetaEventsAllowed(() => {
    this.emit(listenerAdded, {eventName, listener});
  });
}

This would eliminate the need for emit to have a third param and subclasses could do whatever they want. Of course, the downside is that it introduces some global state (but since it wouldn't be exposed to userland maybe it's not so bad?).

Just a rough idea I had; could probably be improved. But if it sounds fine to you then I'll go ahead and make a PR.

from emittery.

Or we can have a special function that emits the meta events on a given emitter instance. Something like this.

👍 Sounds good

from emittery.