Closed outoftime closed 12 years ago
I'd say that this sort of functionality is the reason that attribute_will_change!
is exposed; once you start coloring outside the "property lines", you're responsible for your own dirty tracking. @seancribbs do you concur?
"It's a bicycle accident."
I concur.
This would depend on #241, but anyway, it would be great to do dirty-tracking on dynamically-defined attributes (i.e. attributes not defined as properties, but set on model instances via the
#[]=
method).Here is the relevant bits of the quick patch we're using in our application to handle this: