Update RPC Client #145
Open
Update RPC Client #145
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…kchain interactions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi everyone 😊
I’ve updated the Albatross RPC client to incorporate the patterns and structure I’ve been using over the past year. This PR includes:
The client is no longer class-based—initialize it at startup (see
backend/src/index.tsfor an example).Addresses server changes that aren’t compatible with v0.x.
Details on moving from v0.0.0 to v1.0.0:
https://github.com/onmax/albatross-rpc-client-ts/tree/main?tab=readme-ov-file#migration-guide-from-v000-to-v100
This API isn’t final, so we can refine it before the v1.0 release. I haven’t validated it against your app, but it should work as expected. If you run into any issues or have suggestions, I’d love your feedback!
Thanks for bearing with this breaking change!