-
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
Create LinkButton component #5298
Conversation
🦋 Changeset detectedLatest commit: 2538c7a 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 |
Moving this to ready for review and back into draft for the branch preview - no need to review just yet |
32cc077
to
fcfc107
Compare
Posing a question / addition to the API for anyone reviewing this. A common pattern I observed when I was looking at Next.js repos that consumed the Next.JS Link was that folks would pass in a Node urlObject. Currently this implementation only accepts string as a href, so wondering whether folks think it should also accept that as a type? |
packages/components/src/__actions__/Button/v3/_docs/Button--api-specification.mdx
Outdated
Show resolved
Hide resolved
packages/components/src/__actions__/Button/v3/_docs/Button--api-specification.mdx
Outdated
Show resolved
Hide resolved
packages/components/src/__actions__/Button/v3/_docs/Button--usage-guidelines.mdx
Outdated
Show resolved
Hide resolved
packages/components/src/__actions__/LinkButton/v3/LinkButton.tsx
Outdated
Show resolved
Hide resolved
packages/components/src/__actions__/LinkButton/v3/_docs/LinkButton--api-specification.mdx
Outdated
Show resolved
Hide resolved
packages/components/src/__actions__/LinkButton/v3/_docs/LinkButton--api-specification.mdx
Outdated
Show resolved
Hide resolved
packages/components/src/__actions__/LinkButton/v3/_docs/LinkButton.doc.stories.tsx
Outdated
Show resolved
Hide resolved
packages/components/src/__actions__/LinkButton/v3/_docs/LinkButton--api-specification.mdx
Outdated
Show resolved
Hide resolved
packages/components/src/__actions__/LinkButton/v3/_docs/LinkButton--api-specification.mdx
Outdated
Show resolved
Hide resolved
6fce372
to
0a0f190
Compare
packages/components/src/__actions__/LinkButton/v3/_docs/LinkButton--api-specification.mdx
Outdated
Show resolved
Hide resolved
packages/components/src/__actions__/LinkButton/v3/_docs/LinkButton.doc.stories.tsx
Outdated
Show resolved
Hide resolved
play: async ({ canvasElement }) => { | ||
const canvas = within(canvasElement.parentElement!) | ||
const linkButton = canvas.getByRole("link") | ||
await linkButton.focus() |
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.
It's actually exactly what you're expecting though right? The alternative is to just delete the story. You're right that you're essentially testing RAC functionality, which shouldn't be necessary.
c2c751c
to
d788a4f
Compare
packages/components/src/__actions__/LinkButton/v3/_docs/LinkButton--api-specification.mdx
Outdated
Show resolved
Hide resolved
packages/components/src/__actions__/LinkButton/v3/_docs/LinkButton.doc.stories.tsx
Outdated
Show resolved
Hide resolved
* add missing isDisabled props to LinkButton
d788a4f
to
adf956e
Compare
packages/components/src/index.ts
Outdated
export * from './Menu' | ||
export * from './Button' |
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.
Whoops omg I didn't realise this auto-added itself when I moved things around. Could I trouble you to remove this for me? Since we're currently double exporting 😅 🙏🏻
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.
heheh nice, will axe it :)
17b5304
to
1470490
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.
🚀
Why
This is the counterpart to the Button v3 component and closes the cap on feature parity for the original v1 button.
What