Michael Kelly

@Frederik-Baetens SOrry for the long delay in responding here. By default the gem will attempt to use `cache_key_with_version` or `cache_key` on the object. In a Rails environment this corresponds to...

A PR for this would definitely be welcome!

Those are debug level log messages that the gem emits for easy distinction of what resolved the field in question. You can eliminate the messages by setting your Rails log...

@afuno Did my previous comment answer your question?

@alecgorge I'm sorry it has taken so long to respond to this issue. I no longer work at Stackshare and don't have write access to the repo anymore. That's an...

@jeromedalbert thanks for pointing this out. There seems to be a use case that we don't really cover with overridden keys. Looking through the code, I'm starting to think the...

Starting up a refactor over on #50 that will fix that specific issue along with making it possible to provide a custom key generation class of some kind which will...

Though it's not often used, I think the current implementation is a little stilted in it's flexibility. I think a feature like `cache_if` along with the ability to define a...

cc @bricesanchez

I know this is a bit old, but I recently ran into similar issues...the problem here is that by calling `rspec` or `bundle exec rspec` you are using the executable...