The reasoning is that if it makes sense for ViewModel.find to have the .findOne counterpart, then it makes sense for .children to have a .child too.
So you’re now able to use div($b= "text: child('childVM').someProperty"), but I have a feeling you can probably do it with a reference to the child too.
@manuel I saw a version bump and a video explaining some of the changes, but unfortunately it’s unavailable to me (?).
Perhaps it good to write a little about it here too?
Although I understand @manuel to separate and tunnel questions and issues I do believe that a more active topic in the Meteor forum will give a larger exposure of this great package. Especially since manuel is always active helping out and searching for even better solutions without breaking backwards compatibility. So @avalanche1 I’m with you about that!
Well, of course you guys should do what you feel is best and I’ll be okay with it, but I think a more effective way is to let people know about ViewModel when they ask questions on how to do things with Blaze ("hey, there’s a better way… ")
But it won’t be easily browsable, especially on low end desktops and phones, where Discourse is pretty slow. When I look for solution to particular problem, I can read the topics in help/issues, but I have to dig through the whole thread on forums.
@manuelhttps://viewmodel.meteor.com has been down all day. Is there some other way to view the documentation?
I found a github repo, but it seems to be an old version.
By the way, I love viewmodel. I used blaze components on my last project and viewmodel just makes so many things way easier!
Looks like they moved it to more stable server, the casual *.meteor.com apps are still down, but I see Viewmodel and Blaze Components working fine now.