Comments on: Taking the Pain Out of Complex Forms in Rails http://www.deskchecked.com/2008/07/20/taking-the-pain-out-of-complex-forms-in-rails/ Tom Lee's programming blog Fri, 21 Nov 2008 21:49:05 +0000 http://wordpress.org/?v=2.6.3 By: Eric http://www.deskchecked.com/2008/07/20/taking-the-pain-out-of-complex-forms-in-rails/#comment-1456 Eric Mon, 11 Aug 2008 23:09:15 +0000 http://www.vector-seven.com/?p=77#comment-1456 Yep, was able to get it. Works great, too! Thanks Yep, was able to get it. Works great, too! Thanks

]]> By: Thomas Lee » Fixing Rails Nested Forms (or: HashWithIndifferentAccess is evil) http://www.deskchecked.com/2008/07/20/taking-the-pain-out-of-complex-forms-in-rails/#comment-1450 Thomas Lee » Fixing Rails Nested Forms (or: HashWithIndifferentAccess is evil) Sun, 10 Aug 2008 05:41:11 +0000 http://www.vector-seven.com/?p=77#comment-1450 [...] UPDATE Since I wrote this post, I’ve written a plugin that replaces Rails’ parameter parsing implementation to make dealing with complex nested forms easier still. Refer to Taking the Pain Out of Complex Forms in Rails. [...] [...] UPDATE Since I wrote this post, I’ve written a plugin that replaces Rails’ parameter parsing implementation to make dealing with complex nested forms easier still. Refer to Taking the Pain Out of Complex Forms in Rails. [...]

]]> By: tom http://www.deskchecked.com/2008/07/20/taking-the-pain-out-of-complex-forms-in-rails/#comment-1449 tom Sun, 10 Aug 2008 05:26:03 +0000 http://www.vector-seven.com/?p=77#comment-1449 Eric: is it any better now? Migrated from lighttpd to Apache and I screwed up the configuration. Ivan: Glad you found it useful. :) It's been a thorn in my side a few times in the past. Eric: is it any better now? Migrated from lighttpd to Apache and I screwed up the configuration.

Ivan: Glad you found it useful. :) It’s been a thorn in my side a few times in the past.

]]> By: Ivan http://www.deskchecked.com/2008/07/20/taking-the-pain-out-of-complex-forms-in-rails/#comment-1445 Ivan Sat, 09 Aug 2008 03:39:58 +0000 http://www.vector-seven.com/?p=77#comment-1445 I've been looking for a fix to this problem for months, and attempted writing my own hacked UrlEncodedPairParser with little success. I've tested this plugin in my application and it seems to work perfectly, even with multilevel nested arrays by adding an index option to the block params of the form helper. Might need some hacking to work with Javascript added elements such as in Ryan's complex forms recipe. I would love to see this functionality in Rails 2.2 I’ve been looking for a fix to this problem for months, and attempted writing my own hacked UrlEncodedPairParser with little success. I’ve tested this plugin in my application and it seems to work perfectly, even with multilevel nested arrays by adding an index option to the block params of the form helper.

Might need some hacking to work with Javascript added elements such as in Ryan’s complex forms recipe.

I would love to see this functionality in Rails 2.2

]]> By: Eric http://www.deskchecked.com/2008/07/20/taking-the-pain-out-of-complex-forms-in-rails/#comment-1443 Eric Tue, 05 Aug 2008 18:16:21 +0000 http://www.vector-seven.com/?p=77#comment-1443 I'm having trouble cloning the plug-in with git, and when I click the link to the repo, I receive a 403 error. Any suggestions? I’m having trouble cloning the plug-in with git, and when I click the link to the repo, I receive a 403 error. Any suggestions?

]]> By: tom http://www.deskchecked.com/2008/07/20/taking-the-pain-out-of-complex-forms-in-rails/#comment-1387 tom Mon, 21 Jul 2008 12:58:15 +0000 http://www.vector-seven.com/?p=77#comment-1387 Yep, Koz pointed this out on the mailing list. And yes, it's dealing with part of the same problem. But the parsing itself is the big thing here: <pre><code> ryan = User.create( { :login => 'ryan', :phone_numbers => [ { :area_code => '919', :number => '123-4567' }, { :area_code => '920', :number => '123-8901' } ] }) </code></pre> Try building a form to generate :phone_numbers using edge. It's not a matter of just using "user[phone_numbers][]" or "user[phone_numbers][0]". The former won't work because a "PhoneNumber" has two fields. The latter, because it builds a Hash instead of an Array. The existing form parsing code will limit the usefulness of this new capability. Yep, Koz pointed this out on the mailing list. And yes, it’s dealing with part of the same problem. But the parsing itself is the big thing here:


ryan = User.create( {
  :login => 'ryan',
  :phone_numbers => [
    { :area_code => '919', :number => '123-4567' },
    { :area_code => '920', :number => '123-8901' }
  ]
})

Try building a form to generate :phone_numbers using edge. It’s not a matter of just using “user[phone_numbers][]” or “user[phone_numbers][0]“. The former won’t work because a “PhoneNumber” has two fields. The latter, because it builds a Hash instead of an Array. The existing form parsing code will limit the usefulness of this new capability.

]]> By: Evgeny http://www.deskchecked.com/2008/07/20/taking-the-pain-out-of-complex-forms-in-rails/#comment-1386 Evgeny Mon, 21 Jul 2008 09:07:48 +0000 http://www.vector-seven.com/?p=77#comment-1386 So this new rails edge feature helps you? http://ryandaigle.com/articles/2008/7/19/what-s-new-in-edge-rails-nested-models So this new rails edge feature helps you?
http://ryandaigle.com/articles/2008/7/19/what-s-new-in-edge-rails-nested-models

]]>