-
Notifications
You must be signed in to change notification settings - Fork 1k
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
feat #6772 : defaultVisible prop added #6770
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 2 Ignored Deployments
|
Thanks a lot for your contribution! But, PR does not seem to be linked to any issues. Please manually link to an issue or mention it in the description using #<issue_id>. |
Any update on this ? |
It is assigned to PrimeTek for their review. |
Thank you for bringing this issue to our attention and for your valuable contribution. We truly appreciate the effort you put into this pull request. However, after careful consideration, we have decided to reject the pull request. Our decision is based on the need to maintain synchronization across multiple UI libraries that we are currently developing. Additionally, we believe that this feature might lead to confusion among other users. We hope you understand our decision, and we look forward to any future contributions you may have. |
defaultVisible
Prop to Dialog ComponentFix #6772
This pull request introduces a new
defaultVisible
prop to the Dialog component in our UI library. ThedefaultVisible
prop allows developers to control the initial visibility of the Dialog when the component mounts.Description
The
defaultVisible
prop is a boolean that, when set totrue
, ensures that the Dialog is displayed immediately upon mounting. Conversely, setting this prop tofalse
or omitting it entirely will maintain the default behavior, where the Dialog is hidden initially and requires a trigger to become visible.Changes
defaultVisible
prop to the Dialog component's API.defaultVisible
prop.defaultVisible
prop tofalse
.Usage