Return empty object or null cursor about meteor-publish-composite HOT 9 CLOSED

The find function can return any falsy value (e.g., null, undefined, false, etc) to short circuit. This effectively returns an empty set. You should never call this.ready() or this.stop() in find functions.

For example:

Meteor.publishComposite("mypub", {
    find: function() {
        if (!this.user) {
            return;
        }

        return MyCollection.find({ ... });
    }
});

from meteor-publish-composite.

And what happens if you didn't return nothing? Can that cause problems?

from meteor-publish-composite.

Doing return; is equivalent to return undefined; which is perfectly fine.

from meteor-publish-composite.

Yeah, but what happens if a find doesn't return anything, like:

Find:{
   If(bla){
       return find...
   }
}

from meteor-publish-composite.

Collection.find() always returns a cursor, so that's fine. It doesn't matter if there are records in it or if it's empty.

from meteor-publish-composite.

Sorry, maybe I didn't explain it well but my question was what happens if bla (in this case) is false so collection.find is never fired. No return is called.

from meteor-publish-composite.

Ah, I see. That is also equivalent to return undefined; so no problem.

from meteor-publish-composite.

ok thanks :)

from meteor-publish-composite.

In the native Meteor publish method, returning an empty cursor (i.e. []) works (although this.stop() is best practice) but doing this in publishComposite results in an error, it might be good to replicate this behavior? Although a return statement works. as described above.

from meteor-publish-composite.