-
-
Notifications
You must be signed in to change notification settings - Fork 82
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
fix: issue with collection hooks #404
Conversation
…ing-subscription-initialization
…nitialization Allow checking subscription initialization
Instead the code now checks for a `direct` field on collections and uses that to do lookups; bypassing the (possible) collection hooks
@@ -164,6 +164,9 @@ class RedisSubscriptionManager { | |||
debug( | |||
`[RedisSubscriptionManager] Exception while processing event: ${e.toString()}` | |||
); | |||
Meteor._debug( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Previously these were just swallowed when debug was not turned on
Any chance of fixing the tests? |
BTW, when I tried running the tests locally I ran into a syntax error in Chai because it uses some JS features that are not available in Node v14. I installed |
Once the tests pass I will release it as a patch. |
@jdgjsag67251 some issues still remain. |
Yeah looks like the issue I had with |
This package performs multiple
find
operations. This can cause issues when the Meteor collection hooks package is installed; since this can add restrictions on the selectors which may prevent updates from being sent.This PR just adds a check if the
direct
key is available, if so it will use that for all internalfind
operations.