[patch][need cla] make encodeForm use per-type serialization functions

[ningu]

In my applications I use XMLHTTP-submitted forms frequently, but I prefer to make one small change to how the params are normally submitted -- I make checkboxes always submit 1 or 0, which simplifies handling them on the server end. There is no single thing to override in dojo to create this behavior. I've made a small patch to do so. encodeForm() now chooses its appropriate serializer from dojo.io.formEncodeSerializer[type]. This also allows further customization of form submissions if there is e.g. something special about how you want to handle select-one, or whatever. I've left the image stuff the same cause I wasn't sure what to do with it.

[anonymous]

hi ningu, do we have a CLA on file for you?

If not, would you mind filling one out? http://dojotoolkit.org/icla.txt

Regards

[dylan]

No CLA on file as far as I can tell, so we can't merge this patch.

[dylan]

Pushing to next release because we still haven't received a response to our CLA requirement.

[dylan]

no cla yet, and out of time for 0.4

[jkuhnert]

Re-assigning to james for a minimum of at least getting his thoughts on how this should be handled.

Besides not the not having a cla part, do you even want to see formbind go in this direction?

[James Burke]

No CLA, and there is no form bind in 0.9. Closing this as wontfix since the approach has changed in 0.9.

There is dojo.formToObject, which I do not think should allow special serializers, but instead, use dojo.formToObject to get a JS object representing form values, then you can manipulate that object however you want before serializing.