Skip to content

rpc middleware: introduce separate response types #1546

@niklasad1

Description

@niklasad1

This could be a followup thing to try out but: I wonder whether it's worth now having a separate response type for each call, so that there is no enum?

eg

type CallResponse = ...
type BatchResponse = ...
type NotificationResponse = ...

Originally posted by @jsdw in #1521 (comment)_

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions