[v6.5.0] onBlur, onChange, onDrop, onDragStart not passed into Fields component
See original GitHub issueSee https://github.com/erikras/redux-form/pull/2161#pullrequestreview-14746339
#2161 introduced handler caching. While API for Field
has been fixed by passing these handlers to input
, the Fields
has not been fixed
Issue Analytics
- State:
- Created 7 years ago
- Reactions:4
- Comments:8 (2 by maintainers)
Top Results From Across the Web
[v6.5.0] onBlur, onChange, onDrop, onDragStart not ... - GitHub
While API for Field has been fixed by passing these handlers to input, ... [v6.5.0] onBlur, onChange, onDrop, onDragStart not passed into ......
Read more >Migrating redux-form to v6, onBlur and onChange functions
Object with custom props to pass through the Field component into a component provided to component prop. This props will be merged to...
Read more >ondrop Event - W3Schools
The ondrop event occurs when a draggable element or text selection is dropped on a valid drop target. Drag and drop is a...
Read more >React (forked) - StackBlitz
const attribs = {. type: type || "text",. name: name,. onBlur: onBlur,. onChange: onChange,. onDragStart: onDragStart,. onDrop: onDrop,. onFocus: onFocus,.
Read more >react hook form onblur not working - You.com | The AI Search ...
Name, Type, Description. onSubmit (Default), string, Validation will trigger on the submit event and invalid inputs will attach onChange event listeners to ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Any news on this? We’re getting warnings in the console:
Hi,
It’s a bug. Documentation mentions it as optional
So we should align the prop types (and the flow version?)