Question

Some code that I had that used attr_accessor_with_default in a rails model is now giving me a deprecation warning, telling me to “Use Ruby instead!”

So, thinking that maybe there was a new bit in ruby 1.9.2 that made attr_accessor handle defaults, I googled it, but I don’t see that. I did see a bunch of methods to override attr_accessor to handle defaults though.

Is that what they mean when they tell me to “Use Ruby?” Or am I supposed to write full getters/setters now? Or is there some new way I can’t find?

Answer 1

attr_accessor :pancakes

def after_initialize
     return unless new_record?
     self.pancakes = 11
end

This ensures that the value is initialized to some default for new record only.