我得到了一些像这样的接口:
export interface BroadcastChannel {
name: string;
payload: Record<string, unknown>;
}
export interface TaskWindowCloseChannel extends BroadcastChannel {
name: 'TASK_WINDOW_CLOSE';
payload: {
taskId: number;
};
}
export interface WindowFocusChannel extends BroadcastChannel {
name: 'WINDOW_FOCUS';
payload: {
windowName: string;
};
}它将在函数中使用:
public listenChannel<T extends BroadcastChannel>(name: T['name']): Observable<T> {
const obs = new Subject<T>();
const bc = new BroadcastChannel(name);
bc.onmessage = (ev) => obs.next(ev.data);
return obs.asObservable();
}我希望在这个函数上有一个类型逻辑,每当我在前面的接口中放置'TASK_WINDOW_CLOSE'或name属性的任何其他值时,我都会在observable中使用正确的payload属性类型来键入函数的返回类型。
我希望避免重载,因为将来会有很多类似TaskWindowChannel的接口。
因此,理想的输出应该是:
listenChannel('TASK_WINDOW_CLOSE').subscribe((data: { taskId: number }) => {}); // data type is inferred by name param
listenChannel('WINDOW_FOCUS').subscribe((data: { windowName: string }) => {}); // data type is inferred by name param发布于 2021-07-26 23:06:53
您不能直接实现这一点。但是,您可以利用一个接口来“链接”您的有效负载和您的姓名
interface TaskWindowClosePayload{
taskId: number,
}
interface WindowFocusPayload {
windowName: string,
}
interface MapPayloadNameToType {
'TASK_WINDOW_CLOSE': TaskWindowClosePayload,
'WINDOW_FOCUS': WindowFocusPayload,
};
interface MyBroadcastChannel<T extends keyof MapPayloadNameToType> {
name: T;
payload: MapPayloadNameToType[T];
}现在您可以使用const字符串作为参数:
function foo<T extends keyof MapPayloadNameToType>(name: T): MyBroadcastChannel<T> {
return null as any; // implement and make sure this is correct at runtime!
}
foo('TASK_WINDOW_CLOSE').payload.taskId;其思想是拥有一个类型,其中属性是您的通道名称,而属性的类型是该通道的有效负载的类型。然后,可以使用keyof关键字将这些键作为联合类型获取。
还可以看看jcalz的the comment above,他走的是相反的路线:从联合类型构建名称-类型映射类型。
您可以通过引入更多像type ChannelNames = keyof MapPayloadNameToType这样的类型来添加一些便利,但这会使示例更加复杂。
https://stackoverflow.com/questions/68531894
复制相似问题