Skip to content
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

Complete READMEs for @solana/rpc* #2983

Open
steveluscher opened this issue Jul 25, 2024 · 0 comments
Open

Complete READMEs for @solana/rpc* #2983

steveluscher opened this issue Jul 25, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@steveluscher
Copy link
Collaborator

No description provided.

@steveluscher steveluscher added the enhancement New feature or request label Jul 25, 2024
@steveluscher steveluscher added this to the Release Candidate milestone Jul 25, 2024
steveluscher added a commit that referenced this issue Jul 29, 2024
steveluscher added a commit that referenced this issue Jul 30, 2024
lorisleiva added a commit that referenced this issue Oct 23, 2024
One of the goals of this stack is to eventually make `RpcRequestTransformers` and `RpcResponseTransformers` usable on both RPC and RPC Subscriptions architectures. This was the original intention of the `rpc-transformers` package which already hosts request and response transformers for both but with inconsistent types.

As such, this PR aims to get closer to this goal by moving the `RpcRequest`, `RpcResponse`, `RpcRequestTransformer` and `RpcResponseTransformer` types from the `rpc-spec` package to the `rpc-spec-types` package.

As a reminder the `rpc-spec` and `rpc-subscriptions-spec` packages define the interfaces of the RPC and RPC Subscriptions architectures respectively, whereas, the `rpc-spec-types` package is a utility package that is imported by both of the former packages.

Note that, the `rpc-spec-types` package is now being exported from the main library because re-exporting that package in both `rpc` and `rpc-subscriptions` would be problematic for the main library that re-exports both.

Addresses #2983.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant