Matt Krick

a dependency links the op (usually your viewmodel container) to the model. without flushing deps, your app won't ever know what got updated, and could update when one isn't required....

yeah, an example might be good. whenever dispatch is called, all the invalidated queries will get recalculated.

ah, that's a good catch so the motive is payload reduction, basically create a object of everything you have locally & then remove those things. now if you don't have...

So, let's say each mutation has 3 user-defined methods: ``` const upvoteMutation = { optimistic: (store, optimisticVars) => { return store.entity('Post').get(optimisticVars.id).update((doc) => ({ updatedAt: new Date(), votes: doc('votes') + 1...

@dustinfarris yup. this will largely reduce the scale & complexity of the whole mutations (and eventually subscriptions) API. What's still unclear is how to better handle pagination. I still like...

> but the apollo ecosystem is farther along in featureset if freakin better be, $31MM of VC funding is depending on it 😂 that's _very_ interesting about them denormalizing queries,...

let's stick with the voting example, assume reddit rules where you can only upvote something once. so, you click it twice. Votes go from 0 to 2. The first request...

mutations should _not_ be declarative, this is the error that cashay, relay, and apollo all made. to be declarative means mutating the denormalized state. Since 1 mutation affects many queries,...

> But this is a different world view. For Apollo, the server state/local cache is not (conceptually) part of the Redux store. It requires you to program your reducers such...

How does that work with your 5 in-flight upvote example without an intermediate state? On Feb 16, 2017 5:30 AM, "Wout Mertens" wrote: > So the way I understand Apollo...