This project is archived and is in readonly mode.

Hash.toQueryString
Reported by schnixe | July 21st, 2010 @ 01:46 PM | in 2.0 (closed)
Hash.toQueryString produces ugly php Syntax:
Hash.toQueryString( { a : [1,2,3] } )
->
a[0]=1&a[1]=2&a[2]=3
For what reason? When i use the Element.toQueryString on multiple select options, it results in
a=1&a=2&a=3
why is there a difference? Bug or feature? I'd really prefer the Element.toQueryString on the hash, too :)
schnix
Comments and changes to this ticket
-
Sebastian Markbåge July 21st, 2010 @ 02:59 PM
Yea, we're aware of the problem. This is a difficult one. It's difficult to find a syntax that satisfies everyone's need on the server. Different server-side framework have different requirements.
Ideally, we should also be able to parse it back into an object, non-destructively. Such as in URI.
Meanwhile, this old patch will let you supply a custom format:
http://github.com/calyptus/mootools-core/commit/56905a56648db98c95e...
-
-
Christoph Pojer September 5th, 2010 @ 01:52 PM
- Milestone set to 1.3.0 rc2
- State changed from new to open
- Assigned user set to Valerio
- Milestone order changed from 783 to 0
-
Christoph Pojer September 12th, 2010 @ 03:35 AM
- Milestone changed from 1.3.0 rc2 to 2.0
- Milestone order changed from 78 to 0
-
Valerio September 12th, 2010 @ 03:37 AM
- Milestone changed from 2.0 to 1.3.0 rc2
- Milestone order changed from 804 to 0
-
Valerio September 13th, 2010 @ 01:56 AM
- Milestone changed from 1.3.0 rc2 to 2.0
- Milestone order changed from 1 to 0
right.
-
ibolmo January 19th, 2012 @ 08:06 AM
- State changed from open to invalid
Moved to Github Issues: https://github.com/mootools/mootools-core/issues/2217
Please use Github Issues, since Lighthouse has been deprecated.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »