rubyonrailsin

+1 for this concern.
personally I find the r_c code being DRY at the cost of being not very
readable - A case where I feel more code is better than less.

On Mar 23, 9:41 pm, Michael Guterl <mgut...@gmail.com> wrote:
> 2010/3/23 Jack Lynch <speedyj...@gmail.com>:
>
> > Would it be practical at all to use neither in some situations?
>
> > My reason for asking is that I remember initially finding the controller
> > code within Spree completely baffling.  I'm still not sure I get r_c, but
> > *my impression* of these controller frameworks is that they help achieve DRY
> > code in basic controllers that are backed by one model.  However Spree has
> > some more complex controllers, rhe checkouts controller in particular
> > orchestrates a few models (Order, Checkout, others?) and IMO might be easier
> > to maintain if vanilla Rails code was used instead.
>
> > So, use i_r or r_c in simple scenarios, and live with more lines of code in
> > others for a readability/maintainability benefit?
>
> I have shared a similar opinion in the past and I still agree.
>
> Best,
> Michael Guterl

--
You received this message because you are subscribed to the Google Groups "Spree" group.
To post to this group, send email to spree-user@googlegroups.com.
To unsubscribe from this group, send email to spree-user+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/spree-user?hl=en.