microsoft / microsoft/TypeScript
Disallow excess properties to React components (for performance)
まだ誰も着手していません。
- 主要言語
- Go
- スター
- 111k
- フォーク
- 14.4k
- 平均マージ
- 1日 19時間
- マージ済み PR(30日)
- 117
説明
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.
コントリビューションガイド
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
調査の方向性
まず issue 内の TypeScript と JSX の例を再現し、次に issue #12936 の excess property に関する関連する議論を読んでください。component spread を介して渡された余分な props が型エラーを生成し、既存の関数の動作、JSX のデータ属性、JavaScript の出力には互換性が維持されれば完了です。
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- react, typescript
- 領域
- compilers, frontend
- issue の種類
- 機能追加
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 活発さ
- 停滞
- 明瞭さ
- おおむね明確
- 初心者へのやさしさ
- 28/100