This project is archived and is in readonly mode.
Incorrect input name with nested fields_for
-
josh
- Milestone set to 2.x
- Assigned user set to josh
- Tag set to actionpack
I think that should be the correct behavior. Can you get me a fix too. If not, I'll try to tackle it as well.
-
David Röthlisberger
I am swamped under at the moment, and the rails internals are still black magic to me, so it'll be at least a month before I get around to trying to fix it.
If you can tackle it go ahead, I appreciate it. :)
In the meantime I have worked around the problem by specifying the input name manually, i.e.
fields_for('post[123][comment][]')
instead of
f.fields_for('comment[]')
-
josh
The state of form helpers like this feels very hackish.
I think we should analysis some current patterns and refactor it all.
-
Clemens Kofler
Joshua: I've started refactoring the helpers in my Rails fork at github.com/clemens/rails. There's also a topic in the mailing list (http://groups.google.com/group/r...).
FormHelper is definitely on my list, too. There's also relevant topics here and here
-
RSL
There's been some changes to how index is handled as well. http://rails.lighthouseapp.com/p... has test coverage for indexes on the fields_for. Might be good to mix that in too?
-
josh
- State changed from new to duplicate
