Fix touched behavior

[delesseps]

• Focus and blurring a field with validation rules without changing the value should not cause it to be 'touched'
• Changing a field value back to it's initial value should restore the untouched state

[coveralls]

Coverage increased (+0.7%) to 93.478% when pulling 3300858 on delesseps:master into 4835142 on react-component:master.

[delesseps]

Hi @benjycui, as per the documentation http://react-component.github.io/form/#isfieldtouched(name:-string):-bool, making sure that this works properly. Please take a look.

[delesseps]

@benjycui do you see any issues?

[delesseps]

@afc163 you helped me out with the /switch PR, perhaps you can review this please?

[delesseps]

[jch254]

👍 please merge/review this as I am being affected by this issue too

[benjycui]

Focus and blurring a field with validation rules without changing the value should not cause it to be 'touched'
Changing a field value back to it's initial value should restore the untouched state

I don't agree, touched is not dirty

[benjycui]

It's hard to say which is right.. Could you show other form's behavior?

[delesseps]

We could create a parallel dirty tracking pathway? The dirty state is pretty useful as it can then be used in conjunction with a reset button or used to show warning prompts for preventing route/url changes. What are your thoughts @benjycui?

[delesseps]

Closing for now, will check the state of play in latest ant3

[jch254]

Will check it in ant3 too, thanks for top work squad!