Cache key strict mode

[kevincianfarini]

Use case

My project org has a lot of engineers and we interface with many GraphQL schemas (8 to be exact). It's really easy for someone to introduce a silent bug where they start using a new type from one of the 8 schemas without properly introducing a cache key for it.

This has become more manageable since we've started using declarative cache keys, but the problem is still present. We are finding it difficult to scale enforcement of this and our caching has been suffering as a result.

Describe the solution you'd like

A "Cache Key Strict Mode" would be extremely useful to enforce this. It could allow us to enable strict mode for debug builds. That way if we every attempt to read a value from the cache that does not declare a cache key an exception would be thrown and crash the consuming code.

This would potentially make enforcement of cache keys scale more easily and would easily surface issues to engineers.