A poor choice of words maybe, I was trying to say that at some point in time, I have had models that needed a hierarchy of potential errors and that some errors are not appropriate to show at certain times. A object that goes thru states is a good example.
- Ken On Jun 21, 2012, at 8:32 PM, Rodrigo Rosenfeld Rosas wrote: > Yeah, I couldn't understand what Ken meant by his "state-machine" approach. > > I can't think of a dry way of currently doing that. > > I'm just not much concerned about this as I don't use AR and Sequel's way of > doing validation is by defining a "validate" method, so I'd put my logic > there, but anyway... -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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/rubyonrails-core?hl=en.
