···435435436436In this code example we can first see that the signature of the `updates` entry is very similar to
437437the one of `resolvers`. However, we're seeing the `cache` in use for the first time. The `cache`
438438-object (as [documented in the API docs](http://localhost:3000/docs/api/graphcache/#cache)) gives us
438438+object (as [documented in the API docs](../api/graphcache.md#cache)) gives us
439439access to _Graphcache_'s mechanisms directly. Not only can we resolve data using it, we can directly
440440start sub-queries or sub-writes manually. These are full normalized cache runs inside other runs. In
441441this case we're calling `cache.updateQuery` on a list of `Todo` items while the `Mutation` that