event.preventDefault is not a function in onChange(event, value, previousValue, name)

after upgrade react-redux to version 7.1.1 and redux-form to version 8.2.6… i found that preventDefault object is missing from the event params…

Here is my code…

<Field
     component={ReduxFormRadioGroup}
     formItemProps={{ className: 'operation-hours__option-container' }}
     label='Hours of Operation'
     name='operationHoursCategory'
     onChange={this.handleCategoryChange}
/>

handleDisabledDayChange = (event, value, previousValue, name) => {
        console.log(event, value, previousValue, name)
        event.preventDefault()
        ...
        .......
}

in "redux-form": "^7.2.0" and "react-redux": "^5.0.7": console.log(event) can see the preventDefault: ƒ preventDefault()

in redux-form": "^8.2.6" and "react-redux": "^7.1.1": console.log(event) do not have preventDefault: ƒ preventDefault()

this in result event.preventDefault() is not a function and break the application!

[dereksandkamp]

8.3.0 did not fix the problem for me.

For many of my inputs, I’m calling input.onChange(value) with the value of the input as the argument. These are the inputs that cause the problem. When an onChange is passed to the <Field /> from above these inputs, the first argument injected into the Field’s onChange is the value, not the event. Then there is no way to cancel the change event.

It is possible to fix this by updating my inputs to call input.onChange(event) with the event instead of the value as the first argument. Then any Field.onChange handlers will receive the event. However, this isn’t ideal for some inputs because the value that is attached to the change event is not always the value that I would like to propagate.

There are likely ways to work around this, but it seems like this wasn’t an intended change. Or if it was, the documentation should at least make it clear that in order to receive the event in the Field.onchange handler, you need to pass an event to input.onChange from within the input.

[armin-th]

Just want to note, this is still an issue in 8.3.7

Appreciate any work being put into this 😃