Comments on: Data Persistence on a Multi Page Signup Form in Rails http://blog.jayamster.com/handling-a-multi-page-signup-form-in-rails/2008/09/23/ keeping things simple (hopefully) Fri, 30 Jul 2010 10:43:40 +0000 http://wordpress.org/?v=2.6.3 By: Ryan Platte http://blog.jayamster.com/handling-a-multi-page-signup-form-in-rails/2008/09/23/#comment-4215 Ryan Platte Mon, 15 Jun 2009 14:52:40 +0000 http://blog.jayamster.com/handling-a-multi-page-signup-form-in-rails/2008/09/23/#comment-4215 I was looking to do exactly this to build up a pair of objects in a multi-page flow without rendering form fields for both of them each time. Looks pretty good, thanks for posting it. Comments: Instead of saying value.class == HashWithIndifferentAccess, you can say value.is_a? Hash, since both Hash and HashWithIndifferentAccess respond true to that method call. Also, not a bug but to make the id you could do something like (scope + [key]).join('_'). Finally, if someone's supplying their own keys to reject, I'd replace the default rejections so they get full control. I was looking to do exactly this to build up a pair of objects in a multi-page flow without rendering form fields for both of them each time.

Looks pretty good, thanks for posting it. Comments:

Instead of saying value.class == HashWithIndifferentAccess, you can say value.is_a? Hash, since both Hash and HashWithIndifferentAccess respond true to that method call.

Also, not a bug but to make the id you could do something like (scope + [key]).join(’_').

Finally, if someone’s supplying their own keys to reject, I’d replace the default rejections so they get full control.

]]>