Yeah, good call. The problem with breaking out your logic only to mix it back in is that you haven't really reduced the total complexity of that class, you've just shifted some of it around a bit. Still, they're easier to refactor to without breaking anything, and you can treat the change as an intermediate stage between mess and full class-hood (or just leave them as-is and call it a win).
On Wed, Oct 12, 2011 at 2:15 PM, Paul Annesley <[email protected]> wrote: > On Wednesday, 12 October 2011 at 2:05 PM, Nick Partridge wrote: > > * Large models can have logic broken out into Modules and mixed in. > > .. or preferably split out into separate classes, where that logic is not > part of the same single responsibility. > > -- > You received this message because you are subscribed to the Google Groups > "Ruby or Rails Oceania" 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/rails-oceania?hl=en. > -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" 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/rails-oceania?hl=en.
