Todor Grudev

I can give a hand too :+1:

Feature request should be more specific, please take the time to provide information on why you think it's going to be helpful and some use case scenarios. Thank you!

Hello @raix , did you manage to dig into this ? I have a project with GroundDB and appcache - Once I log in I do GroundDB(Meteor.users) (on the client...

Would very much appreciate that :) :+1:

Hmm I've managed to make it work nothing is different though - I just put the GroundDB('users') -> inside lib/collections/users.coffee and I publish the user collection. Now I can't reproduce...

@satyavh I know it's not the best solution but currently for this case I am using [caolan/async](https://github.com/caolan/async) - here's an example: I want to update 2 records from different Collections...

So currently I am handling the iron router waitOn problem by checking the Meteor.status().connected otherwise I rely on the grounded data. Is this a good idea ?

yes I am doing the same thing :) until the intelligent sub is on :+1:

The last version of ground:db is 0.3.14, can you be more specific where and on what occasion this happens? Some code would be nice too.

I was thinking the same, is there a possibility to use rails-api stack on a namespaced resource ?