It looks like we should use
getMeteorData as high up the stack as possible, same as
state. From the example I’ve seen, this is where we subscribe as well as make a fetch. Now, let’s say the child component doesn’t need that fetched data, but the grandchild component does. Should I pass it through the child as a
getMeteorData again in the grandchild, or go directly to the source (eg use
Collection.findOne() in a method)?
It seems like the 3rd option, although the easiest, kills the whole notion of loose coupling. However, if that grandchild component makes a
Meteor.call I don’t know any other way to do it, since I want to get a trustworthy document from the server. Any guidance?