Andrew Geweke

@ajb — this is great! I’ve been spending a lot of time thinking about this, and I’m currently leaning towards the idea of making caching a separate `gem` that layers...

OK, I just went spelunking down quite the rabbit-hole. I have a question for you, and then a broader discussion: **Question**: What specific case was failing for you that caused...

Re: test suite — let me know if I can help. I saw the issue you open/closed around `bundler exec`, but happy to help with anything else. Re: `virtual_path` —...

Ah, excellent. That does make sense. You shouldn’t actually need to include `CacheHelper` at all — helpers should be available to you automatically in any Fortitude widget. If you remove...

OK, awesome! Glad to hear it. Re: `render :widget` and `cacheable`…it’s really up to you. Without `@virtual_path` set, Rails caching _does_ still work, and works fine; the only difference seems...

Re: your last comment — #43 doesn't actually add the Rails helpers to every view. All it does is change it so that if Fortitude’s `automatic_helper_access` setting is `false`, you...

Re: caching and `@virtual_path`. I’ve been thinking about this one quite a bit. The problem of stale views is going to be there, unfortunately, no matter what you do. Even...

Whoops, I got confused…I’d explained that bit of madness to other people before in different threads, but not you. My apologies! Take it as evidence that it trips up _everyone_....

Scott! How are you? Drop me a line ([`[email protected]`](mailto:[email protected])) sometime. I’m sorry it took me so long to respond — I’ve been furiously preparing for a through-hike of the Pacific...