-
Notifications
You must be signed in to change notification settings - Fork 424
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should the "*" event handlers be fired last? #26
Comments
Next version will do this, I agree. |
I also been thinking this. And I'm still not sure. For me it make sense to be first, haha. |
I think the only real difference from my perspective would be what each option enables. The only thing I can think of is that firing Thought: we should do whatever WildEmitter does, they were one of the first to do a |
Yea, it seems that they fire wildcards after. Checked. :) So yea current master is wrong. |
kk, I think I'm good with after in order to keep things matchy-matchy. I know that's a little arbitrary, but I feel like they probably already had lots of discussion around the ordering, project is over 2 years old last I checked. |
This would be useful when you want to run some cleanup function or 'catch all' after all of your matching event handlers have been called.
The text was updated successfully, but these errors were encountered: