-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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(www): Unnecessary AlertDialogPortal and DialogPortal component removed #1603
Conversation
@iam-rohid is attempting to deploy a commit to the shadcn-pro Team on Vercel. A member of the Team first needs to authorize it. |
Hmmm it looks like this was removed but released as a patch in radix-ui/primitives#2178 I'll review and merge. |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
Thank you.
Thanks for merging 😀 |
Fixes #1595, #1644 This PR changes the components that use the `DialogPortal` element to be aliases rather than components that pass a className prop. The `DialogPortalProps` type from `@radix/react-dialog` recently had a patch update that probably should have been a minor or maybe a major update which is causing a few people to see the error `Property 'className' does not exist on type 'DialogPortalProps'`. Since the `DialogPortal` component doesn't actually output any DOM elements, it never technically supported the `className` prop and the fact that it surfaced that prop was really a bug. The `AlertDialog` and `Dialog` components were updated in #1603, but the `Sheet` component still references `className` which is resolved in this PR.
Fixes shadcn-ui#1595, shadcn-ui#1644 This PR changes the components that use the `DialogPortal` element to be aliases rather than components that pass a className prop. The `DialogPortalProps` type from `@radix/react-dialog` recently had a patch update that probably should have been a minor or maybe a major update which is causing a few people to see the error `Property 'className' does not exist on type 'DialogPortalProps'`. Since the `DialogPortal` component doesn't actually output any DOM elements, it never technically supported the `className` prop and the fact that it surfaced that prop was really a bug. The `AlertDialog` and `Dialog` components were updated in shadcn-ui#1603, but the `Sheet` component still references `className` which is resolved in this PR.
Fixes shadcn-ui#1595, shadcn-ui#1644 This PR changes the components that use the `DialogPortal` element to be aliases rather than components that pass a className prop. The `DialogPortalProps` type from `@radix/react-dialog` recently had a patch update that probably should have been a minor or maybe a major update which is causing a few people to see the error `Property 'className' does not exist on type 'DialogPortalProps'`. Since the `DialogPortal` component doesn't actually output any DOM elements, it never technically supported the `className` prop and the fact that it surfaced that prop was really a bug. The `AlertDialog` and `Dialog` components were updated in shadcn-ui#1603, but the `Sheet` component still references `className` which is resolved in this PR.
There are unnecessary
AlertDialogPortal
andDialogPortal
components inalert-dialog
anddialog
. And they are accepting className props which is not required inAlertDialogPortal
andDialogPortal
component from radix-ui. So, I have removed them.