Odd setFieldTouched behavior

Question?

Hitting something odd with setFieldTouched that I can’t quite figure out. I’m passing down setFieldTouched from withFormik to some inputs, and then doing:

handleBlur = () => {
  const { name, setFieldTouched } = this.props;
  setFieldTouched(name, true); // name = 'start'
};

Oddly, in some instances, this call is setting an object instead of just setting a bool:

Here is the error:

And here is the value of touched:

If I change the call to this:

handleBlur = () => {
  const { name, setFieldTouched } = this.props;
  setFieldTouched(name); // Note, no second arg
};

Then my touched looks correct:

Just curious why the second argument of setFieldTouched could be creating an object instead of just setting the value?

• Formik Version: 1.0.0-alpha.1
• React Version: 16.2.0
• OS: Ubuntu 16.04
• Node Version: 8.4
• Package Manager and Version: yarn 1.5.1

[arist0tl3]

Were you able to have a look at the sandbox repo? The touched values are following what is set in the initial mapPropsToValues:

[stale[bot]]

ProBot automatically closed this due to inactivity. Holler if this is a mistake, and we’ll re-open it.