-
Notifications
You must be signed in to change notification settings - Fork 23
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
fix(Menu): Pass onClick through even when rendered as a link #4845
Conversation
🦋 Changeset detectedLatest commit: 3219da5 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
d3dd991
to
5546c7e
Compare
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.
@dougmacknz I think Cass was saying if we rebase off main and force push to the branch this will (hopefully) pass chromatic. Holler if you want me to give that a crack :)
nvm, commented just as you did 😆 |
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.
Looks hunky dory - I think the story flagged in chromatic wasn't picked up when it got merged last time so probs why its in the diff
Why
No reason to block this, it's needed in some cases where you want to do something before navigating, like tracking. Best to still keep the element as a link in the DOM in this case.
What
Currently,
onClick
is not being passed through in the case that MenuItem has anhref
and renders a link