Humn, i've already got a project where I could use atleast two blocks of default options in more than one model. it would certainly make them arrid extra-DRY!
I completly agree that we should open this up, away from without_* towards a complete options scope On Jan 14, 10:49 am, Michael Klishin <[email protected]> wrote: > On 14.01.2009, at 13:42, heda wrote: > > > Yeah, I see what you're saying. default_property_options should > > probably be a block though rather than a method to allow different > > sets of defaults > > block will sure give you more flexibility, but how often would you > need it? > I personally have an app with 50+ models and I never used many sets of > default values, > usually just one, that I already implemented as > default_property_options in a plugin not yet open sourced. > > MK --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DataMapper" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/datamapper?hl=en -~----------~----~----~----~------~----~------~--~---
