microsoft / microsoft/TypeScript
Disallow excess properties to React components (for performance)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
Search Terms
react excess props properties component function parameters
Suggestion
import * as React from 'react';
import { ComponentType } from 'react';
type Props = { foo: 1 };
declare const MyComponent: ComponentType<Props>;
declare const propsWithExtras: Props & { bar: 1 };
// Expected error, but got none
<MyComponent {...propsWithExtras} />;
I understand this matches TypeScript's behaviour with functions:
type Props = { foo: 1 };
declare const MyFunction: (props: Props) => void;
declare const propsWithExtras: Props & { bar: 1 };
// No error
MyFunction(propsWithExtras);
MyFunction({ ...propsWithExtras });
However, with React, passing excess props to a component is a performance concern, since those excess props may break component memoization, causing the component to update more frequently than it should.
In my experience, this error most often occurs when wrapping components, where the wrapper components need to "pass through" types to a child:
type MyComponentProps = { foo: 1 };
declare const MyComponent: ComponentType<MyComponentProps>;
type MyWrapperComponent = MyComponentProps & { myWrapperProp: 1 };
const MyWrapperComponent: ComponentType<MyWrapperComponent> = props => (
<MyComponent
// We're passing too many props here, but no error!
{...props}
/>
);
Workarounds I'm aware of: (1) avoid spreading, but this quickly becomes a non-option when a component has many props you have to manually pick and pass through.
const MyWrapperComponent: ComponentType<MyWrapperComponent> = ({ foo, myWrapperProp }) => (
// Error as expected due to excess prop `myWrapperProp`
<MyComponent foo={foo} myWrapperProp={myWrapperProp} />
);
(2) Pass through props via an object.
type MyWrapperComponent = { myComponentProps: MyComponentProps } & { myWrapperProp: 1 };
const MyWrapperComponent: ComponentType<MyWrapperComponent> = ({ myComponentProps, myWrapperProp }) => (
// Error as expected due to excess prop `myWrapperProp`
<MyComponent {...myComponentProps} myWrapperProp={myWrapperProp} />
);
However then we lose special JSX behaviour such as the ability to pass data attributes as props.
IIUC, this could be a use case for https://github.com/Microsoft/TypeScript/issues/12936.
Checklist
My suggestion meets these guidelines:
- This wouldn't be a breaking change in existing TypeScript/JavaScript code
- This wouldn't change the runtime behavior of existing JavaScript code
- This could be implemented without emitting different JS based on the types of the expressions
- This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
- This feature would agree with the rest of TypeScript's Design Goals.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the TypeScript and JSX examples in the issue, then read the related excess-property discussion in issue #12936. Done means excess props supplied through a component spread produce a type error while existing function behavior, JSX data attributes, and JavaScript output remain compatible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- compilers, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100