I've noticed several places in the code that issue a findOne(or other find method), without using a cache, but then don't do any modifications to the returned value. Such call sites should really use a caching variant of the delegator.
What I'd like to work on, is a feature, only used during development, that would record any value looked up that wasn't cached, and wasn't later modified, and print a warning, with an exception, to allow for a caching variant to be added. Would others find this useful? Obviously, it would need to be transaction based, and would sometimes have false-positives. Additionally, if no transaction is active, then that automatically means a caching variant should be used.
