PropTypes in a TypeScript React Application
Does using React.PropTypes make sense in a TypeScript React Application or is this just a case of "belt and suspenders"?
Since the component class is declared with a Props type parameter:
interface Props {
// ...
}
export class MyComponent extends React.Component<Props, any> { ... }
is there any real benefit to adding
static propTypes {
myProp: React.PropTypes.string
}
to the class definition?
Answer
Typescript and PropTypes serve different purposes. Typescript validates types at compile time, whereas PropTypes are checked at runtime.
Typescript is useful when you are writing code: it will warn you if you pass an argument of the wrong type to your React components, give you autocomplete for function calls, etc.
PropTypes are useful when you test how the components interact with external data, for example when you load JSON from an API. PropTypes will help you debug (when in React's Development mode) why your component is failing by printing helpful messages like:
Warning: Failed prop type: Invalid prop `id` of type `number` supplied to `Table`, expected `string`
Even though it may seem like Typescript and PropTypes do the same thing, they don't actually overlap at all. But it is possible to automatically generate PropTypes from Typescript so that you don't have to specify types twice, see for example: