Type useState as array of strings in React TypeScript
To type a hook in React useState
as an array of strings, use generics for hooks, e.g. const [names, setNames] = useState<string[]>([])
state variables can be initialized to an empty array or an array of strings, and only accept string values.
import {useState} from 'react';
const App = () => {
// 👇️ const names: string[]
const [names, setNames] = useState<string[]>([]);
return (
<div>
<button onClick={() => setNames(prevNames => [...prevNames, 'Bob'])}>
Add name
</button>
{names.map((element, index) => {
return (
<div key={index}>
<h2>{element}</h2>
</div>
);
})}
</div>
);
};
export default App;
We use generics to correctly type the useState hook, while initializing the hook with an empty array.
If we hadn't used a generic, e.g. useState<string[]>([])
type hook, the type of the state variable would be never[]
, in other words, an array that would never contain any elements.
Even if you pass an empty string to the array, TypeScript will be able to infer the type of the state variable.
import {useState} from 'react';
const App = () => {
// 👇️ const names: string[]
const [names, setNames] = useState(['']);
return (
<div>
<button onClick={() => setNames(prevNames => [...prevNames, 'Bob'])}>
Add name
</button>
{names.map((element, index) => {
return (
<div key={index}>
<h2>{element}</h2>
</div>
);
})}
</div>
);
};
export default App;
请注意
, we don’t even have to use generics to type our state variables. TypeScript is able to infer the type based on the initial value provided.
However, it is best to always explicitly type
useState
your hooks, especially when working with arrays and objects.
If we try to add a value of a different type to the state array, we will get a type checking error.
import {useState} from 'react';
const App = () => {
// 👇️ const names: string[]
const [names, setNames] = useState<string[]>([]);
// ⛔️ Argument of type '(prevNames: string[]) => (string | number)[]' is not
// assignable to parameter of type 'SetStateAction<string[]>'.
setNames(prevNames => [...prevNames, 1000]);
return (
<div>
<button onClick={() => setNames(prevNames => [...prevNames, 'Bob'])}>
Add name
</button>
{names.map((element, index) => {
return (
<div key={index}>
<h2>{element.toUpperCase()}</h2>
</div>
);
})}
</div>
);
};
export default App;
This example shows how attempting to add a number to string[]
a state array of type can cause an error in the type checker.
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
How to avoid cross-origin (CORS) issues in React/Next.js
Publish Date:2025/03/17 Views:166 Category:NETWORK
-
In this article, we will introduce how to avoid cross-origin (CORS) issues in React/Next.js. Cross-origin resource sharing (CORS) is a protocol that defines how web requests should be handled when crossing different URLs.
React Tutorial - Transferring Props
Publish Date:2025/03/16 Views:185 Category:React
-
React transfers Props. Props are generated when components are encapsulated. Components expose some properties (Props) to the outside world to complete some functions.
React Tutorial: Props Anti-Pattern
Publish Date:2025/03/16 Views:183 Category:React
-
React's Props anti-pattern, using Props to generate state in getInitialState is an anti-pattern - Anti-Pattern.
React Tutorial - Props Validation
Publish Date:2025/03/16 Views:99 Category:React
-
Props validation is a very useful way to use components correctly. It can avoid many bugs and problems as your application becomes more and more complex. In addition, it can make your program more readable.
React tutorial: Types of Props for child components
Publish Date:2025/03/16 Views:170 Category:React
-
Usually, the child components of a React component are a group, that is, the child components are an array. Introduction to Type of the Children Props.
How to solve the error Uncaught TypeError: Cannot read properties of undefined in
Publish Date:2025/03/16 Views:150 Category:React
-
In the process of React development, we often encounter some errors. Here we look at an error reported in App.js. The error is as follows: App.js:69 Uncaught TypeError: Cannot read properties of undefined (reading 'setState') at onInput
Why do you need to bind event handlers in React Class Components?
Publish Date:2025/03/16 Views:58 Category:React
-
When using React, we must have come across control components and event handlers. We need to use `.bind()` in the constructor of the custom component to bind these methods to the component instance. As shown in the following code:
Solution to the error "does not contain a default export" in React
Publish Date:2025/03/16 Views:187 Category:React
-
When we try to use `default import` to import from a module that does not have a `default export`, we get a "does not contain a default export" error. To fix the error, make sure the module has named exports and wrap the import in curly braces, e.g.
Error in React: Attempted import error 'X' is not exported from Solution
Publish Date:2025/03/16 Views:76 Category:React
-
In React, the error “Attempted import error 'X' is not exported from” in React.js occurs when we try to import a named import that does not exist in the specified file. To fix the error, make sure the module has named exports and you have not obfu