Assign FormData fields back to form? Any interest? about formdata

[anddoutoi]

I really like the gist of this idea. We sometimes (using React/Redux) store a full FormData instance in the store and it would be very convenient if we could just take props.formData and apply it to a <form>. The contract would be very strong in this case. Now we do this in a custom way.

I'm not sure I like the getter/setter approach and I generally prefer not to dabble with built-in prototypes even if it's supported by most UAs today. This operation could be "costly" and a function/method call shows this better then just a setter. Using a function also enables you to have an optional iteratee handler if you need to make something custom.

I also guess that the scope needs to be limited to static forms and the handling of dynamically added form controls and values can be considered in a 2.0.

[jimmywarting]

I want to built it independent of any framework (jQuery, Angular, React, Vue) so it can work in any project.

I'm still wondering if you sometimes need a custom iteratee handler. or if you need custom options.
The way it should work is just doing the opposite thing to what new FormData(form) dose

I was also thinking what if the element don't exist? should it create a <input type="hidden"> with it's value? or only assign it to the element that dose exist.

[anddoutoi]

Agree on that is should be completely framework agnostic. I was just emphasising how we are using FormData (and by that, this polyfill).

I was also thinking what if the element don't exist? should it create a with it's value? or only assign it to the element that dose exist.

Kind of depends of the purpose of the feature. To fill in a form from a FormData object or make a 1-to-1 mapping for network transport?

In a first version I would say that it should not mutate the markup or try to do some "smart things".