-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Button: Making all MenuButton props optional #8975
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
Button: Making all MenuButton props optional #8975
Conversation
This feels like it would have required some code changes.. I wonder if |
Component perf results:
|
Hello @khmakoto! Because this pull request has the Do note that I've been instructed to only help merge pull-requests of this repository that have been opened for at least 8 hours, a condition that is not currently met. No worries though, I will be back when the time is right! 😉 p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me and give me an instruction to get started! Learn more here. |
@msft-github-bot wait 15 minutes |
Hello @khmakoto! Because you've given me some instructions on how to help merge this pull request, I'll be modifying my merge approach. Here's how I understand your requirements for merging this pull request:
If this doesn't seem right to you, you can tell me to cancel these instructions and use the auto-merge policy that has been configured for this repository. Try telling me "forget everything I just told you". |
Pull request checklist
$ npm run change
Description of changes
This PR makes all of
MenuButton
props optional so that they don't have to be necessarily provided by the users of the component. This change was spurred by this comment in #8754.Focus areas to test
(optional)
Microsoft Reviewers: Open in CodeFlow