-
-
Notifications
You must be signed in to change notification settings - Fork 752
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
SocketIO event filtering #50
Conversation
This is probably the biggest feature for the next release so we should make sure that this works nicely. /cc @Glavin001, @ekryski |
This will be great! I'll try and test it out tomorrow. |
So #51 is based on this PR and implements the whole thing for Primus which I think should finalize this functionality. |
If there are no comments or concerns I'll merge this one and #51 in tonight so that we can get a 0.4.0 out this week. |
👍 I looked over all of the changes and everything looked good. I have not had a chance to personal test it, but I didn't notice any missing Tests either and Travis CI is still happy. |
* chore(package): update semistandard to version 11.0.0 https://greenkeeper.io/ * Fix for latest Semistandard
* chore(package): update semistandard to version 11.0.0 https://greenkeeper.io/ * Fix for latest Semistandard
* Rename repository and use npm scope * Update debug dependency
* Rename repository and use npm scope * Update debug dependency
This pull request implements event filtering for SocketIO. Letting you filter events based on the connected client information. For example the following only dispatches the
updated
event if the authorized user is in the same company than the updated todo:On the client:
Closes #44, closes #48.