- Issue created by @brianperry
- Assigned to pratik_kamble
As we add the ability to get an individual resource by ID, we could encounter a case where a requested resource could be satisfied from a cached collection. Since resources and collections will have unique cache keys, the caches for resources and collections are essentially handled separately.
We could solve this problem, but it will likely also increase the complexity of our cache logic quite a bit. So we'll need to consider the priority of this. Should we solve it in this package, or should we provide a method for provided caches to implement this behavior. Or do nothing?
Active
Code