流星发布/订阅混乱

Question

So, in my server.js I have the following code to limit what the client receives:

Meteor.publish('customerList', function()
{
    return Meteor.users.find({roles: 'customer'}, {fields: {profile: 1}});
});

I only want to find users with 'roles' of value 'customer', using the Roles package. Then on the client.js I do ANOTHER find() in a subscribe:

Meteor.subscribe('customerList', function()
{
    var foundCustomers = Meteor.users.find().fetch();

    Session.set('foundCustomers', foundCustomers); //i have a Session.get elsewhere which returns this cursor
});

And ofcourse in my template I show these values like this:

<template name="customer_search_result">
    {{#each customers}}
        <div>{{profile.firstname}} {{profile.lastname}}, {{profile.tel}}</div>
    {{/each}}
</template>

So what am I doing wrong when I am seeing all of the different roles in this list now? If I add the same rules in my subscribed find() as in my published then we get no result at all.

Answer 1

Your publish and template look fine, you just need to change your subscribe like this:

Meteor.subscribe('customerList');

Then you need a template helper like so:

Template.customer_search_result.helpers({
    customers: function(){
        return Meteor.users.find({roles: 'customer'}, {fields: {profile: 1}});
    }
})

Answer 2

Since there is another publication which publishes the employee s, you'll need to take just the customer s from Meteor.users in the subscribe callback, otherwise you might get some employee s as well. First, add roles to the published fields (I assume this isn't a problem):

Meteor.publish('customerList', function()
{
    return Meteor.users.find({roles: 'customer'}, {fields: {profile: 1, roles: 1}});
});

Then update the subscribe function:

Meteor.subscribe('customerList', function()
{
    var foundCustomers = Meteor.users.find({roles: 'customer'}).fetch();
    Session.set('foundCustomers', foundCustomers);
});

By the way, by fetch ing the cursor and storing the results in the session, you will break reactivity. If this is intentional - you just want a once-off snapshot of the customers - you should consider stopping the subscription after you're done with it, otherwise the server will keep sending new customers to the client which are never used:

var customerListSubscription = Meteor.subscribe('customerList', function()
{
    var foundCustomers = Meteor.users.find({roles: 'customer'}).fetch();
    Session.set('foundCustomers', foundCustomers);
    customerListSubscription.stop();
});

If you want reactivity, see Kelly Copley's answer.