Lio*_*Tay 4 typescript reactjs
我正在尝试对 React 组件的 props 使用联合类型
type Props =
| {
type: "string"
value: string
}
| {
type: "number"
value: number
}
| {
type: "none"
}
class DynamicProps extends React.Component<Props> {
render() {
return null
}
}
// Ok
const string_jsx = <DynamicProps type="string" value="hello" />
// Error as expected, value should be a string
const string_jsx_bad = <DynamicProps type="string" value={5} />
// Ok
const number_jsx = <DynamicProps type="number" value={5} />
// Error as expcted value should be a number
const number_jsx_bad = <DynamicProps type="number" value="hello" />
// Error as expected, invalid isn't a property on any of the unioned types
const extra = <DynamicProps type="string" value="extra" invalid="what" />
// No error? There should be no value when type="none"
const none_jsx = <DynamicProps type="none" value="This should be an error?" />
// Ok, seems like value has become optional
const none2_jsx = <DynamicProps type="none" />
// Error as expected, value is not present. Value doesn't seem to be made optional all the time
const required = <DynamicProps type="string" />
Run Code Online (Sandbox Code Playgroud)
它似乎部分起作用,因为type有效道具会根据道具而改变。然而,虽然未出现在联合中任何类型上的额外属性将是一个错误,但至少出现在一个联合类型中但根据判别属性不属于的类型似乎不会是一个错误。错误。
我不知道为什么会这样。使用联合类型作为反应组件的道具是一种反模式吗?
问题与工会参与时过多的财产检查有关。您可以在此处阅读类似问题的答案。其要点是,对联合的多余属性检查允许任何成员的任何键出现在对象上。我们可以通过引入 never 类型的额外成员来解决这个问题,以确保具有多余属性的对象不会错误地与特定成员兼容:
type Props =
| {
type: "string"
value: string
}
| {
type: "number"
value: number
}
| {
type: "none"
}
type UnionKeys<T> = T extends any ? keyof T : never;
type StrictUnionHelper<T, TAll> = T extends any ? T & Partial<Record<Exclude<UnionKeys<TAll>, keyof T>, never>> : never;
type StrictUnion<T> = StrictUnionHelper<T, T>
class DynamicProps extends React.Component<StrictUnion<Props>> {
render() {
return null
}
}
// error now
const none_jsx = <DynamicProps type="none" value="This should be an error?" />
Run Code Online (Sandbox Code Playgroud)
| 归档时间: |
|
| 查看次数: |
2823 次 |
| 最近记录: |