Open wildhart opened 4 years ago
My suggestions for resolving this:
Tracker.autorun
to set a session variable to turn userCache off within that session...; orMeteor.methods
to set a session variable to turn userCache on only with methods.Or, is there a better way of detecting whether the current fibre is running in a method or publication?
Had time for a bit more research. Seems you can tell if you're in an autorun with just Tracker.active
. The docs say that it's only available on the client, but it works for me on the server even if I uninstall peerlibrary:reactive-publish.
So I suggest changing this:
Meteor.user = function (input) {
if (typeof input === "undefined") {
return _original();
}
to this:
Meteor.user = function (input) {
if (typeof input === "undefined" || (Tracker && Tracker.active)) {
return _original();
}
That fixes it for me.
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:
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.