Optimistic mutation results

[micimize]

This depends on #114 - a naive implementation shouldn't be too difficult.
Steps for optimistic results would be:

• Add an list of optimistic result patches to the cache
• associate them with mutations and invalidate them appropriately

Offline queue moved to #201:

@HofmannZ if #114 makes sense to you I'd like to start working on it in preparation to implement this

[HofmannZ]

@micimize Yeah sounds good to me, need any help?

[micimize]

@HofmannZ possibly! I think I've just about completed the optimism chunk of this, continuing from #130 (although they're less entangled than I expected).

Here's a brain dump on the query rebroadcast logic, for posterity:
The solution I implemented is to just rebroadcast all safe queries from the cache on every optimistic update, preserving previous QueryResult state where it makes sense.

Apollo's solution, which may be more robust:

• call a protected broadcastWatches method on the cache when optimistic updates are made
• this calls a callback supplied in the query manager with the change diff,
  marking the query invalidated
• invalidated queries are then broadcast when broadcastQueries is called immediately after optimistic results are recorded.
• they are then marked valid again in listeners (which there is always one of)

[eusdima]

Fixed by #130

[micimize]

this was not actually resolved - #114 was resolved, which was a dependency.

Here's a diff of the most recent work I've done on this

[micimize]

closed by #199

[HofmannZ]

🎉 This issue has been resolved in version 1.0.0-beta.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[HofmannZ]

🎉 This issue has been resolved in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀