3 ms·
I'd love for it to be part of standard rails, but don't they usually like to see features like this play themselves out as gems before trying to incorporate the
by nate 14y ago
I'd love for it to be part of standard rails, but don't they usually like to see features like this play themselves out as gems before trying to incorporate them (e.g. turbolinks, cache-digests, etc.).
Of course if anyone knows of a better way, please don't hesitate to let me know or ping someone on rails core.
- steveklabnik 14y agoAs the newest Rails committer, I'd suggest that you post to the rails-core list to discuss it, that's how things would work. I haven't looked into your implementation, but if it just makes things faster, and doesn't change semantics, then rolling it right into Rails is feasible. It's new features-semantics that are generally 'new gems.'
- nate 14y agoThanks Steve, I'll do that. All it does is add an extra option (or two) to the views render method. By default nothing changes. Stuff only gets invoked if someone wants to do: render partial: thing, collection: @things, cache: true
- steveklabnik 14y agoHmm, yeah, then it might be gem-worthy. Can't hurt to talk about it on the list!