Add a function createReactiveStoreFromRpcAndSubscription#1528
Merged
Conversation
🦋 Changeset detectedLatest commit: 7fc0245 The changes in this PR will be included in the next version bump. This PR includes changesets to release 46 packages
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 |
Member
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
This was referenced Apr 8, 2026
BundleMonFiles updated (4)
Unchanged files (138)
Total files change +1.72KB +0.35% Final result: ✅ View report in BundleMon website ➡️ |
Contributor
|
Documentation Preview: https://kit-docs-nofv92u3r-anza-tech.vercel.app |
lorisleiva
approved these changes
Apr 8, 2026
Member
lorisleiva
left a comment
lorisleiva
left a comment
There was a problem hiding this comment.
Nice! I love that you can wrap a reactive store in another reactive store whilst providing an RPC pending request for the initial fetch. 👌
mcintyre94
force-pushed
the
rpc-subscriptions-w-slot
branch
from
2cfa212 to
cbdcf38
Compare
mcintyre94
force-pushed
the
subscriptions-reactive
branch
from
632c232 to
20263d3
Compare
mcintyre94
changed the base branch from
subscriptions-reactive
to
graphite-base/1528
mcintyre94
force-pushed
the
graphite-base/1528
branch
from
20263d3 to
f53ce07
Compare
mcintyre94
force-pushed
the
rpc-subscriptions-w-slot
branch
from
cbdcf38 to
efcc9b8
Compare
This creates a reactive store that combines an RPC and RPC Subscription, that can both map to the same data type. It exposes the latest value from either source, by slot comparison.
mcintyre94
force-pushed
the
rpc-subscriptions-w-slot
branch
from
efcc9b8 to
7fc0245
Compare
This was referenced Apr 8, 2026
Merged
Closed
Contributor
|
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. |
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Problem
In my earlier PR I added an API to get a reactive store (subscribe, getState, getError) for RPC subscriptions. But another case, which is more complex for apps, is where you want to get the current state and then keep it updated with a subscription. An example of this was the balance functionality in our react app, which makes a call to
getBalanceand then subscribes to account updates, and keeps track of the slot to always accept only the most recent data. Just having a reactive subscription is insufficient for this use case.Summary of Changes
This PR adds a new function
createReactiveStoreFromRpcAndSubscription. It's added topakcages/kitsince it combines RPC and subscriptions.It takes as input:
SolanaRpcResponse, ie provides a slot in contextTItemSolanaRpcResponse, providing a slot in contextTItemIt then returns a
ReactiveStoreas defined in the previous PR which provides the latest data (by slot number) from either data source, and notifies subscribers only when newer data is available (or an error occurs). It handles the unified abort signal and error handling.This generalises the approach used in
balance.ts, while providing an output shape compatible with any reactive framework.The PR also updates the
balance.tsin the react-app to demonstrate this, binding the store to an SWR subscription.This would enable frameworks targeting react, SWR, or any other reactive library etc to provide bindings like
useBalance()with minimal framework logic.Outside of balance, it would be useful for any case where we have an RPC and a subscription providing the same data that can change. Anything on accounts (getAccountInfo + account notifications), and potentially also transaction signatures (
getSignatureStatuses+ signature notifications).I also realised afterward that we could provide an async generator API for this, which only yields values when the slot is newer. Same logic, but presented as an async generator API. I'll add that later as a follow up PR.