-
Notifications
You must be signed in to change notification settings - Fork 910
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename RpcResponse
to RpcResponseData
#3145
Conversation
🦋 Changeset detectedLatest commit: f16d5af The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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.
2473269
to
cd9b1b2
Compare
cd9b1b2
to
f16d5af
Compare
Merge activity
|
Because there has been no activity on this PR for 14 days since it was merged, it has been automatically locked. Please open a new issue if it requires a follow up. |
The purpose of this PR stack is to refactor both the RPC and RPC Subscriptions packages such that they have better interfaces with their respective transports. In this first batch of PRs, we will start by focusing on the RPC packages whilst ensuring minimum changes on the RPC Subscriptions packages.
The end goal of this first part is to have the following interfaces for the RPC packages:
RPC Shared Layer
RPC Transport Layer
RPC API Layer
RPC Layer
In the first two PRs of the stack, we start by cleaning up the type namespace to allow these new types to exist. First, we rename
RpcResponse
toRpcResponseData
, sinceRpcResponse
will be used to define a proper response interface that aligns all the RPC layers.