Meteor.publish('coins', function(address) { // process data according to address parameter
return Coin.find({ address: address }, { fields: Coin.publicFields })
}
Then in the client:
meteor: {
$subscribe: {
'coins': function() {
return [this.$route.params.id] // send the param to the server
}
},
coins() {
return Coin.find({}) // looks redundant but it's necessary. Tells the client to read all the documents sent by the server.
}
},
Without the find criteria you may retrieve more documents from the minimongo collection than you wished for. Remember you can have more than one subscription for the same collection active at any one time.
To add on to that, start looking at your subscriptions as if they are clients fetching from endpoints. Minimongo is just the store where that data ends up. Multiple endpoints store documents in the same store.