-
Notifications
You must be signed in to change notification settings - Fork 10
Conversation
@@ -2,14 +2,17 @@ import * as rpc from "../../../rpc/mod.ts"; | |||
import { effector, EffectorArgs } from "../../impl/mod.ts"; | |||
|
|||
export interface RpcClientR<Beacon> { | |||
rpc: rpc.RpcClientFactory<Beacon>; | |||
rpc: rpc.RpcClientFactory<Beacon, rpc.RpcError>; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ignore the fact that we specify the wide rpc.RpcError
instead of piping the error types through the top-level rpcClient
effect. We'll get to this later (#46).
rpc/Base.ts
Outdated
|
||
export abstract class RpcClient { | ||
/** Send a message to the RPC server without |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
without what?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice catch
super(); | ||
} | ||
} | ||
export abstract class RpcClient<RpcError extends E.RpcError> { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this generic on the error?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My thinking is that we'll want beacon-specific error types (web sockets can error out differently from Smoldot client instances).
No description provided.