Apologies in advance if this is off topic, but after deciding strong params didn't work well with my particular use case I decided to write this: https://github.com/ismasan/parametric
I understand it might be overkill for most cases but I wonder if Rails' built-in solution could benefit from a rethink of the strong-params DSL along similar lines. On Tuesday, 6 May 2014 01:36:03 UTC+1, Alexander Trauzzi wrote: > > WRT my example, try two required params in the child structure instead of > just one then ;) > > A part of me thinks require was designed in haste and a regression - while > never pleasant - shouldn't be ruled out this early in the game. > > Two methods will have to exist after all is said and done for sure. But > just because anyone has standardised around a potentially bad design and > has no problems with it doesn't vindicate that it is making people do very > obscure and esoteric things with params. It's still a bad design imposing a > requirement on your request schema. > > Broken windows being what they are.... > > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/d/optout.
