microsoft / microsoft/TypeScript
Disallow excess properties to React components (for performance)
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- Go
- Sterne
- 111k
- Forks
- 14.3k
- Ø Merge
- 2 T. 4 Std.
- Gemergte PRs (30 T.)
- 132
Beschreibung
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.
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Beginne damit, die TypeScript- und JSX-Beispiele im Issue zu reproduzieren, und lies dann die verwandte Diskussion zu excess properties in Issue #12936. Als erledigt gilt die Aufgabe, wenn überschüssige Props, die über einen component spread übergeben werden, einen Typfehler erzeugen, während das bestehende Funktionsverhalten, JSX-Datenattribute und die JavaScript-Ausgabe kompatibel bleiben.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- react, typescript
- Bereich
- compilers, frontend
- Issue-Typ
- Feature
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 28/100