Loren ☺️

Nice, can you repair the cached doc with observed changes, or do you refetch or delete? On Monday, May 23, 2016, Sashko Stubailo [email protected] wrote: > You know what would...

Ah, yes – it's observeChanges that only gives the fields http://docs.meteor.com/api/collections.html On Monday, May 23, 2016, Sashko Stubailo [email protected] wrote: > I think observe just gives you the whole new...

Pseudocode for this: https://github.com/apollostack/meteor-integration/pull/19#issuecomment-228629726

I'm not sure what that error is, sorry! If you wanted to reproduce in a fork of this repo, I'd take a look: https://github.com/lorensr/test-meteor-apollo

Oh cool! Didn't know you could do that with Mongo. Not sure if the speed improvement is worth the added complexity—perhaps the rare cases in which the JS logic is...

We would use `context.userId` in our own code, but maybe we're calling a library that assumes the presence of `Meteor.userId` on the server.

Thanks—do you see any downsides to reusing withUser everywhere instead of using it once at the top and prop drilling? On Sun, Jun 17, 2018 at 6:28 AM Prosper Otemuyiwa...

Okay, here's the plan! I'm liking it a lot. Lmk if you have any further thoughts @unicodeveloper @jeresig - direct user query - login/logout: globals - `loginInProcess` status: apollo-link-state -...

Turned out to be simpler—given deduplication and default `cache-first` fetch policy, there's no point to the `fetchUserData` and `fetchPolicy: 'cache-only'`

Why not use `Meteor.userId()` for methods? Don't know where `collection-hooks` gets the `userId` from, but if ^ works in methods, I would imagine `collection-hooks` should also work.