What I've found is that DRY is good until it leads to the point of obscurity...
I use a standard partial to handle the hidden fields for routing users to the appropriate place after an add or update (if you add a B from A, you should go back to A. if you added the B from C, you go back to C, etc). As long as the partials are named descriptively and can lead another developer easily to the correct source, "DRY"ness is in the eye of the beholder... -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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-talk?hl=en -~----------~----~----~----~------~----~------~--~---
