Think about special kind of Hook that would allow implementing resolvers cache.

[pie6k]

No description provided.

[pie6k]

I was thinking about this a bit and actually, I've changed my mind to NOT add this.

I'm starting to have strong opinion that caching should be domain of resolver function itself. Adding some 'top-layer' for such scenario might be good for some, but limiting for others.

While I believe @before and @after hooks have some reasonable use-cases, another type of hooks that is able to interrupt resolver workflow might be wrong direction.

I'd see typegql more like library with as transparent as possible API rather than framework.

If there will be no external input about it, I'll close issue without adding such Hooks.