Update wallet standard docs #21447
Open
Update wallet standard docs #21447
Conversation
This file contains 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
Update docs link
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Skipped Deployments
|
github-actions
bot
added
the
Type: Documentation
hayes-mysten
approved these changes
Mar 10, 2025
|
This change looks good, thanks for updating these! Can we clean up the commit history so that we just have a single commit before merging? |
Thank you! Yeah, sure. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Updated import names in documentation to use the
Standard*prefix in accordance with the latest changes in@mysten/wallet-standard.The following updates were made:
ConnectFeature→StandardConnectFeatureConnectMethod→StandardConnectMethodEventsFeature→StandardEventsFeatureEventsOnMethod→StandardEventsOnMethodThis is a documentation update only, with no functional changes.
Test plan
No testing required as this is a documentation update.
Release notes
No release notes required as this change only affects documentation.