Fix the value prop on input should not be null error in React
The warning "value prop on input should not be null" is caused when we set the initial value of an input to null or override the initial value setting it to null, for example from an empty API response. Use a fallback value to solve this problem.
Here is an example of how this can result in a warning.
export default function App() {
// ⛔️ Warning: `value` prop on `input` should not be null.
// Consider using an empty string to clear the component or `undefined` for uncontrolled components.
return (
<div>
<input value={null} />
</div>
);
}
The problem in the above code sample is - we set the value attribute of the input field to null, which is not allowed.
We might also get the value of the input field from a remote API and set it to null.
To fix this, we must ensure that the value property on the input is never set to null by providing a fallback value.
import {useState} from 'react';
const App = () => {
// 👇️ 将空字符串作为初始值传递
const [message, setMessage] = useState('');
const handleChange = event => {
setMessage(event.target.value);
};
// ✅ 使用 fallback, 例如
// value={message || ''}
return (
<div>
<input
type="text"
id="message"
name="message"
onChange={handleChange}
value={message || ''}
/>
</div>
);
};
export default App;
We initialize the value of the state variable to an empty string instead of null.
This will silence the warning unless the state variable is set to null somewhere else in your code.
We have used a logical OR (||)
operator that returns the value on the right if the value on the left is false (such as null).
This helps us ensure that the value attribute of the input field is never set to null.
If using uncontrolled input fields with refs, don't set value
the attribute on the input at all, use defaultValue
.
import {useRef} from 'react';
const App = () => {
const inputRef = useRef(null);
function handleClick() {
console.log(inputRef.current.value);
}
return (
<div>
<input
ref={inputRef}
type="text"
id="message"
name="message"
defaultValue="Initial value"
/>
<button onClick={handleClick}>Log message</button>
</div>
);
};
export default App;
The example above uses an uncontrolled input. Note that the input field has no onChange
attributes or values set.
We can pass an initial value to an uncontrolled input using the defaultValue property. However, this is not required and you can omit the prop if you don’t want to set an initial value.
When using uncontrolled input fields, we access the input using ref.
Each time the user clicks the button in the example, the value of the uncontrolled input is recorded.
We should not set the attribute on uncontrolled inputs ( onChange
input fields without a handler) value
because this will make the input field immutable and we won't be able to type in it.
For reprinting, please send an email to 1244347461@qq.com for approval. After obtaining the author's consent, kindly include the source as a link.
Related Articles
Fix Uncaught ReferenceError: useState is not defined in React
Publish Date:2025/03/15 Views:142 Category:React
-
When we use the useState hook in our code but forget to import it, it generates the error Uncaught ReferenceError: useState is not defined. To fix this error, you need to import the hook before using it import {useState} from react . // ?️
React error Uncaught ReferenceError: process is not defined solution
Publish Date:2025/03/15 Views:116 Category:React
-
要解决 React 中的“Uncaught ReferenceError: process is not defined” 错误,需要在项目的根目录中打开终端并通过运行 `npm install react-scripts@latest` 更新 `react-scripts` 包的版本,并在必要时重新安装
How to solve the "Function components cannot have string refs" error in React
Publish Date:2025/03/15 Views:138 Category:React
-
当我们在函数组件中使用字符串作为引用时,会出现错误“Function components cannot have string refs”。 要解决该错误,需要使用 useRef() 钩子来获取一个可变的 ref 对象,我们可以将其用作组件
React Error Property 'X' does not exist on type 'Readonly<{}>'
Publish Date:2025/03/15 Views:139 Category:React
-
当我们尝试访问未键入的类组件的 props 或状态时,会发生 React.js 错误“Property does not exist on type 'Readonly '”。 要解决该错误,需要使用 React.Component 类上的泛型来输入该类的道具或状
Solve React's Unexpected default export of anonymous function error
Publish Date:2025/03/15 Views:119 Category:React
-
当我们尝试使用默认导出导出匿名函数时,会导致“Unexpected default export of anonymous function”警告。 要解决此错误,需要在导出函数之前为其命名。
React error Type '() => JSX.Element[]' is not assignable to type FunctionCompo
Publish Date:2025/03/15 Views:51 Category:React
-
当我们尝试从函数组件返回元素数组时,会发生 React.js 错误“Type '() => JSX.Element[]' is not assignable to type FunctionComponent”。 要解决该错误,需要将元素数组包装到 React 片段中。
How to solve React Type {children: Element} has no properties in common with type
Publish Date:2025/03/15 Views:103 Category:React
-
React.js 错误“Type {children: Element} has no properties in common with type IntrinsicAttributes” 当我们尝试将 children 道具传递给不带任何道具的组件时发生。 要解决错误,需要定义并键入组件上的属性
Property does not exist on type 'JSX.IntrinsicElements' error in React
Publish Date:2025/03/15 Views:188 Category:React
-
When the name of a component starts with a lowercase letter, an error "Property does not exist on type 'JSX.IntrinsicElements" will appear. To fix this error, you need to make sure you always start your component names with an uppercase letter, instal
React uses Router to get the current route
Publish Date:2025/03/15 Views:99 Category:React
-
Use the `useLocation()` hook to get the current route through React Router, such as `const location = useLocation()`. The hook returns the current location object. For example, we can access the pathname as location.pathname.