-
Notifications
You must be signed in to change notification settings - Fork 157
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
docs: update structure for Wallet
docs
#1581
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Wallet
docsWallet
docs
site/docs/pages/wallet/wallet.mdx
Outdated
}, ]} /> | ||
|
||
### ConnectWallet | ||
Handles the wallet connection process. Place child components inside to customize the connect button appearance. |
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 need to standardize on what we call the "child components". in other docs we refer to them as subcomponents, and children below references "customized content"
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.
I am in support of standardizing around the following:
- Components that we ship are subcomponents (e.g. ConnectWallet, NFTMedia, etc)
- children the user passes in are just
children
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.
In this case though, I'm in favor of removing "Place child components inside...", it feels unnecessary when the children
prop is right there in the table.
What changed? Why?
This PR updates the structure for our documentation to make it easier for developers to scan through available props and sub-components.
Adds:
Notes to reviewers
How has it been tested?