On Mon, Aug 9, 2010 at 8:08 AM, RichardOnRails <[email protected]> wrote:
>> I'd suggest that it's good practice to handle any (even nil) input value >> in a way appropriate to your business logic. > > I've code exactly the logic I wanted, except for how to enforce that a > vendor be selected from the drop-down before creating a new expense > record. Which you cannot do. You can "know" absolutely nothing about what happens on the client side; all you can do is handle the requests that you receive. Which may not include parameters that you're hoping to see :-) Hence my suggestion that your code deal appropriately with those situations, however unlikely you might think they are. Good luck, -- Hassan Schroeder ------------------------ [email protected] twitter: @hassan -- 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.
