huh, React yells if you use onInput instead of onChange

pull/2451/head
Richard Harris 6 years ago
parent 099e3d7eed
commit 4bf5f63086

@ -57,18 +57,18 @@ export default () => {
const [a, setA] = useState(1); const [a, setA] = useState(1);
const [b, setB] = useState(2); const [b, setB] = useState(2);
function handleInputA(event) { function handleChangeA(event) {
setA(+event.target.value); setA(+event.target.value);
} }
function handleInputB(event) { function handleChangeB(event) {
setB(+event.target.value); setB(+event.target.value);
} }
return ( return (
<div> <div>
<input type="number" value={a} onInput={handleInputA}/> <input type="number" value={a} onChange={handleChangeA}/>
<input type="number" value={b} onInput={handleInputB}/> <input type="number" value={b} onChange={handleChangeB}/>
<p>{a} + {b} = {a + b}</p> <p>{a} + {b} = {a + b}</p>
</div> </div>
@ -121,7 +121,7 @@ In Vue, your markup must be wrapped in a `<template>` element, which I'd argue i
In React, we have to respond to input events ourselves: In React, we have to respond to input events ourselves:
```js ```js
function handleInputA(event) { function handleChangeA(event) {
setA(+event.target.value); setA(+event.target.value);
} }
``` ```

Loading…
Cancel
Save