Expected Behavior? about eventemitter2 HOT 7 CLOSED

I am unable to reproduce this, there are a few possibilities. 1) not all my code is committed properly (I've been traveling while working on this), 2) I've not published latest to npm (or you need to update from npm), 3) make sure you git pull from head. Let me know

from eventemitter2.

I see...

I'm using the latest 'master' commit 9757112
fyi.

from eventemitter2.

Hmmm, also the cases above works for the latest npm version.

If you work with a dirty HEAD beyond npm releases, please omit this, otherwise i think that is a problem to fix :)

fyi, again...

from eventemitter2.

looking at this now that im back.

from eventemitter2.

Issue 1 resolved. Working on issue 2.

from eventemitter2.

Heh. Issue 2 is expected behavior.

['foo','bar','baz'] !== ['foo','*']
['foo','bar','baz'] === ['foo','*','*']

I am lead to believe that you desire the wild card to mean "everything after, unconditionally". The current behavior models the unix file-system wild-card style, its segment explicit, rather than arbitrary. I'm open to changing this if people want it.

from eventemitter2.

Hi, issue1 seems to be solved, thanks!

Personally if we talk about the 'namespace' concept, i expect the wildcard matches 'everything after, unconditionally'. And i suppose that we are talking about 'Namespaced events' in a programmatic manner imho.

But of course, your choice is your flavor all time.

from eventemitter2.