Rails 3 compatibility #4
Conversation
|
Whoops, didn't notice the other pull request for Rails 3. Mine seems a lot more compact and targeted but I'm not sure if I'm covering anything or just the subset of functionality our app uses. |
|
+1 for compact and targeted |
|
@lmc, after speaking to the authors regarding gemification and maintenance, I am now maintaining (with the authors' permission) a rails 3+, ruby 1.9+ -compatible gem version on my branch. I'd have kept it on in the plugin format but Rails 4 is abolishing vendored plugins, so I thought I'd get ahead of the curve and get it into a gem. The gem is named "object-daddy" because some gentleman apparently deployed an older gem named "object_daddy", then subsequently disappeared. Attempts to contact him have been for naught, so taking over the originally-named gem is out of the picture for the time being. Of course, you're welcome to keep rolling as you please, just thought I'd let you know. :) |
3 participants
Hey, I did a little fix-up to get this working on Rails 3. It seems to work for me and all the specs still pass.