Removing properties in Ripple

Sean Cribbs sean at
Wed Feb 9 09:05:03 EST 2011


A little git history helps. It seems you added that spec back in November, I think around the time we were discussing how to properly deal with the "_type" property in #instantiate. Without remembering too much of the original context, the question seems to be: should it silently ignore attributes that no longer exist on the model or should it warn the programmer in some way that a property doesn't exist? The current code seems to favor the latter, in the form of a NoMethodError.

Sean Cribbs <sean at>
Developer Advocate
Basho Technologies, Inc.

On Feb 9, 2011, at 8:44 AM, Duff OMelia wrote:

>> I don't know the original intent but it would be nice to have
>> some sort of deprecated_property declaration that allows using the
>> data attributes and can possibly have options for migration, like
>> keep, delete, log or a proc that could transition it to a new
>> attribute.
> I'd also be fine doing things "manually" for awhile to give the code a
> chance to reveal the abstraction.  I'm still mulling on the best way
> to even do it manually. :)
> ------------------------------------------------------------
> Duff OMelia
> _______________________________________________
> riak-users mailing list
> riak-users at

More information about the riak-users mailing list