Improve Documentation for Forms

[PolGuixe]

I can't see in the Docs a good alternative to:

const {input1, input2} = this.refs;
submitMethod(input1.getValue(), input2.getValue());

How can a value be obtained from the <FormControl/> component?

[jquense]

you can just use findDOMNode on the component to get the underlying input

[nmn]

The switch from the old Input to Form Controls has many downsides. This being just one more.

[taion]

getValue was a broken API in that it wasn't compatible with any sort of HoCs like from Redux. That you can now use getDOMNode to get the DOM node from the <FormControl> no matter how you wrap it was one of the explicit goals here.

[vinnymac]

I understand that we can now use getDOMNode and ReactDOM.findDOMNode to get the node from the FormControl. In fact I think this is better for everyone, and seems to follow a more react friendly way of obtaining the node. However the name of this issue is Improve Documentation for Forms, which I don't believe has been taken care of.

I only knew to make this change in my projects because I found these issues. I think it would be better to leave this open until documentation for explaining this is added, unless of course we expect people to just assume this is what they need to do from now on.

[jquense]

PRs Welcome! we'll happily take a doc improveent

[chalda]

I still dont see any end-to-end examples of how to work with values in FormGroups. You mention using findDOMNode but I don't quit understand how to do this easily.

this jsfiddle is probably the most example code I found on the net and it works with inputs directly:
http://jsfiddle.net/mnhm5j3g/1/

I think I might just have to rewrite everything with plain .

[jquense]

@chalda there is nothing special to be done about managing values, the FormControl's are just wrappers around the plain inputs, so you do the same things to manage values as you would plain inputs

[Industrial]

Hi!

first of all thanks to everyone who contributed to this project. It's an enormous help for people trying to bust out apps world wide I think.

I'm now converting an old codebase to a new version of this, and I'm changing all the <Input>'s into <FormControl>'s.

I've never worked with findDOMNode before but the documentation had a big fat WARNING saying it's not a good idea to be using it. I tried to but I'm not sure I understand the API. It seems to be taking a Component, would that be the this inside a component definition/class?

It would be highly beneficial for me for the documentation to include small code examples how "how to get stuff done", and in my experience leaving things implied will always get some reader/user in trouble down the line :-)