All the more reason why we need some solid, concrete use cases.

On May 27, 2014, at 8:23 PM, Sean Griffin <notifications@github.com> wrote:

> In activerecord/test/cases/custom_properties_test.rb:
> 
> > @@ -4,6 +4,7 @@ class OverloadedType < ActiveRecord::Base
> >    property :overloaded_float, Type::Integer.new
> >    property :overloaded_string_with_limit, Type::String.new(limit: 50)
> >    property :non_existent_decimal, Type::Decimal.new
> > +  property :string_with_default, Type::String.new, default: 'the overloaded default'
> The point here is to allow the user to hook into a lower level API, and simplify it overall. The main focus of the refactorings required to make this possible were focused on removing behavior based on symbols and replacing it with objects. I think that using symbols for the API to specify the type instead of an object seriously undermines that. I know @tenderlove and I spoke briefly about this as well. Thoughts?
> 
> —
> Reply to this email directly or view it on GitHub.
>