-
-
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
add possibility to filter listen event on server #32
Comments
and can you look issues that closed, but I have add some additional comment |
Yes, I've been thinking about how to do this properly, too. Debating of adding an event dispatching mechanism where you can decide if the event + object combination should be sent to a connected client. |
Following up on it here: #44 (comment) |
* chore(package): update primus to version 6.0.5 * Update Primus compatibility * Switch to UWS for testing * Add missing dependency
* chore(package): update primus to version 6.0.5 * Update Primus compatibility * Switch to UWS for testing * Add missing dependency
updating error handler to be more HTML friendly
* Update to Feathers v3 * Prepare prerelease * Revert verifier
* fix(package): update passport-jwt to version 3.0.0 * Compatibility with passport-jwt 3.0 * Remove package-lock.json, will be added later * Add package-lock.json back
* Fix header casing * Fix test cases and Readme
* Update to Feathers v3 * Prepare prerelease * Revert verifier
* fix(package): update passport-jwt to version 3.0.0 * Compatibility with passport-jwt 3.0 * Remove package-lock.json, will be added later * Add package-lock.json back
* Fix header casing * Fix test cases and Readme
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue with a link to this issue for related bugs. |
some thing like that:
The text was updated successfully, but these errors were encountered: