Using with react-datepicker about react-use-form-state HOT 6 CLOSED

All these forms for onChange should be supported:
onChange(e)
onChange(e, value)
onChange(value)

from react-use-form-state.

Does this work? (Adopted from the readme's advanced input section). The text/textarea/select/etc functions the hook gives are basically just spreading an object into the component with all of the things (value, id, etc) the input needs. So if everything's named "correctly" it should JustWork™.

 <DatePicker
        {...text({
          onChange: date => doTheThing(date) /* or (e, value) => {...}, or... */,
          onBlur: () => {} /* Dunno if you'd need to "no op" this */ ,
        })}
      />

Here's a list of the props DatePicker takes, if they're not called the same you might have to wrap the text function and remap some of the property names?

Remapping should be as simple as defining a mapProps function that looks like:

function mapProps({prop1, prop2 /* (and so on) */ }) {
  return { newName1: prop1, newName2: prop2, ... } // and so on
}

and then using it like <input {...mapProps(text(...))}.

from react-use-form-state.

No it doesn't. As I said, the problem is that useFormState's handler tries to get the value from e.target.value while in this example e is undefined. And the onChange handler for helpers like text() is not overriding the default onChange behavior, it's just there to help us do side effects.

from react-use-form-state.

Ahh, I see now. Sorry for misreading. I thought the onChange was for overriding it, but looking at the source I can see where I missed that. It seems to me that having the onX handlers override things would be the most intuitive approach. But the default handler looks quite tightly coupled to the internal mechanisms of the hook... I don't see an immediately obvious fix for that, unfortunately.

from react-use-form-state.

I was looking at this exact problem, too (although in my case, the library is react-select).

It seems like one solution to this would be to do add some handlers for "raw" types. Something along the lines of:

export default function SignUpForm() {
  const [formState, { text, raw }] = useFormState();
  return (
    <form onSubmit={() => console.log(formState)}>
      <input {...text('name')} />
      <DatePicker {...raw('date')} />
    </form>
  );
}

So raw() would return, to use some typescript annotation, a:

interface Raw<T> {
    onChange(value: T): void;
    value: T;
    onBlur(): void;
}

?

from react-use-form-state.

Or,

export default function SignUpForm() {
  const [formState, { text, raw }] = useFormState();
  return (
    <form onSubmit={() => console.log(formState)}>
      <input {...text('name')} />
      <DatePicker {...date('date', {raw: true})} />
    </form>
  );
}

Although this doesn't work as nicely for this example, since DatePicker gives us an actual Date, not a string.

from react-use-form-state.