subscribing to related tables?

[dcsan]

this is more a question i guess, but just asking here as the docs are a bit thin. perhaps i can add the answer to the README

this package will give you nice shortcut methods to bring in related items.
but it won't handle the subscriptions
additionally we now need to manage both the Collection and the Minimongoid instance.

so i'm wondering whats a best practice pattern or recommended way to do this?
eg if I have comments and users

comment.user.name

won't work on its own. i still need to do

u = comment.user
sub = Meteor.subscribe("Users", {_id: U._id } )  # and wait for callback or react

also when workign with collections, I cannot directly subscribe to a collection name but instead I need to deal with the instance.@_collection

This all seems like a lot of work, and maybe i'm missing the point of minimongoid.
once you get past a toyapp where you aren't subscribed to all the data all the time,
having access to the shortcut method names isn't that useful if they never have any data in them?

perhaps these relations could be wrapped up in the package, but then we're getting to a "X with relations package". so i guess the minimongoid use case is for lighter simple joins where you know the data ahead of time and just want the syntactic sugar?