Although given that the view path was derived from the mode’s class name, you could argue that it already was. I’ve had need of this feature for rendering diverse collections of objects, so I’m glad to see it implemented.

That’s something else altogether. #cache_key is a bona fide general purpose model method; it’s the model identifying itself a short name that’s consistent in certain conditions.

#to_partial_path, by contrast, is strongly tied to the ActionView layer. Were it an ActiveRecord method, I’d be bothered, but Jose rightly points out that it’s ActiveModel, so could and should be implemented on presenter objects instead of AR objects.

Does a model defining #cache_key which can be leveraged by view code  also break concerns? I do not think so.

Can you explain a bit. I hope this is useful .