-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
feat: rust client account resolvers #2814
base: master
Are you sure you want to change the base?
feat: rust client account resolvers #2814
Conversation
@levicook is attempting to deploy a commit to the coral-xyz Team on Vercel. A member of the Team first needs to authorize it. |
Supporting account resolution in Rust clients would be great, thanks for starting this! However there is one problem — I'm working on a massive PR that is related to the IDL and account resolution which I'm planning to finish later this month. Would you be able to wait until that lands so that we can avoid running into a bunch of conflicts? |
Thanks for the heads up! I started this with an intention to get a feel for the concrete problem. No urgency on my end & it would be helpful to track your work -- do you have an open PR I can follow? We can close the PR. I'll leave my branch open to keep experimenting. Totally fine for it to go stale & invalid. We'll start fresh after your work lands. |
One realization already is that we might be able to just generate better client code up front & skip network calls to retrieve idls that may or may not be published. |
Not yet but I can let you know when I do. |
Here is the PR: #2824 |
for now, this is just me looking at what it would take to catch the rust client up with the typescript client's ability to derive accounts from an idl. if it goes well, i'll clean the description up & make it not a draft.