I have the following failing test case in
actionpack/test/controller_test.rb (edge):
{{{
def test_deep_query_string_with_array_of_hashes_with_hash_values
query_string = ‘x[y][][z]=1&x[y][][w][a]=2&x[y][][w][b]=3’
assert_equal(
{“x” => {“y” => [{“z” => “1”, “w” => {“a”=>“2”, “b”=>“3”}}]}},
ActionController::AbstractRequest.parse_query_parameters(query_string)
)
end
<{“x”=>{“y”=>[{“w”=>{“a”=>“2”, “b”=>“3”}, “z”=>“1”}]}}> expected but was
<{“x”=>{“y”=>[{“w”=>{}, “z”=>“1”}, {“w”=>{}}]}}>.
}}}
The deeply-nested query strings like the one above arise from
correspondingly deeply-nested forms, built using fields_for, that allow
users to create complex models with all of their associations at once.
I’d like to be able to have that form functionality, but not have to
resort to hacking the params layout.
Does the test cast above make sense - i.e. is the expection reasonable?
If so, does anyone have any thought on how to tackle this problem?
Perhaps this is just too must nesting?