-
Notifications
You must be signed in to change notification settings - Fork 200
chore: add the links to the components for sdk and site #1557
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
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
How to use the Graphite Merge QueueAdd the label graphite-merge-queue to this PR to add it to the merge queue. You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. |
🌿 Documentation Preview
|
| * This hook is used to create a SolanaSigner instance. | ||
| * It is used to sign transactions and messages for the Solana blockchain. | ||
| * | ||
| * ```tsx |
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.
Adding some docs
| toAddress: "<toAddress>", | ||
| }, | ||
| * ``` | ||
| function MyComponent() { |
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.
Wanted to have something that had the types, and was checked
| } | ||
| ``` | ||
|
|
||
| ## Other examples |
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.
We probably should remove this, I didn't know where to put, then I found that the components where already being rendered
| "useClientActions", | ||
| "useChain", | ||
| ], | ||
| "Solana Actions": ["useSolanaTransaction", "useSolanaSignMessage"], |
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.
This was the biggest aha moment
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.
@moldy530 What about the provider? Should I make a context or make it part of the other alchemy provider, and should I add this in as a seperate config field, or part of chain setup, which I have to filter now I think for viem vs not
| - page: useSolanaTransaction | ||
| path: wallets/pages/reference/account-kit/react/hooks/useSolanaTransaction.mdx | ||
| - page: useSolanaSigner | ||
| path: wallets/pages/reference/account-kit/react/hooks/useSolanaSigner.mdx |
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.
should this be useSolanaSignMessage.mdx instead of useSolanaSigner.mdx?
Pull Request Checklist
yarn test)sitefolder, and guidelines for updating/adding docs can be found in the contribution guide)feat!: breaking change)yarn lint:check) and fix any issues? (yarn lint:write)PR-Codex overview
This PR introduces support for Solana actions in the
@account-kit/reactlibrary, enhancing the functionality for handling Solana transactions and integrating them into the existing account kit structure.Detailed summary
"Solana Actions"section with hooks:useSolanaTransactionanduseSolanaSignMessage.useSolanaTransactionwith examples and parameters.AlchemySolanaWeb3Contextwith detailed usage instructions.SolanaSignerclass with methods for signing and transaction handling.