-
Notifications
You must be signed in to change notification settings - Fork 7
Description
If Meteor.user([fields]) doesn't hit the cache then the result is _original() which is reactive. However, if it hits the cache then the result is static (not reactive).
This is fine within a method, but if this is used within a reactive-publish, the resulting publication will not react to changes in the specified fields.
Somehow this package needs to detect if it is running inside an autorun and if so always return the _original() reactive function.
A common use-case for reactive-publish is to only publish documents the logged-in user has permission to see, e.g. in a multi-tenancy SaaS application, or in a chat room:
Meteor.publish("usersInChatRoom", function() {
// Need to put this in an autorun in case user switches room
this.autorun(function () {
const user = Meteor.user('roomIds'); // oops, employed userCache out of habit...
return user
? Meteor.users.find({roomIds: {$in: user.roomIds}}, {fields: ...})
: null;
});
})In this example, when a user changes room the publication will not change. This is a contrived example and a bit of an edge-case, but it could happen. So far only luck has saved me from suffering this bug in production - fortunately I was requesting a field which isn't published to the client so userCache was never hitting the cache. If I remove the private field then I can reproduce this bug easily.