I'm wrestling with the best way to handle what is probably a somewhat common situation with controller actions and creating a new model instance. I need to split the :new action into two parts.
The creation of a new :proposal instance is really a two-step operation. The first step sets up some basic features of the new :proposal and the second step lets the user enter all of the details (lots of nested attributes and other stuff). The question is, how should this be handled in a controller? Short of adding a proposals_controller#setup action that then redirects to :new, is there a more canonically correct way to do this? My Google-fu is letting me down on this, mostly because I'm having trouble describing what the problem is that I'm trying to solve. I'm going to bring this issue to the Hackfest this Thursday night as well. Thanks, Chris -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby
