Closed iamtouha closed 8 months ago
The latest updates on your projects. Learn more about Vercel for Git ↗︎
Name | Status | Preview | Comments | Updated (UTC) |
---|---|---|---|---|
tremor-storybook | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Jan 5, 2024 2:19pm |
:tada: This PR is included in version 3.13.0-beta-dialog.1 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
Hey @iamtouha, thank you very much for creating this PR. I merged it a few days ago and its almost ready to be included in our next release.
Today I wanted to update Headless UI from 1.7.17
to1.7.18
and in the updated version, there seems to be a type issue. I am having a hard time fixing it, could you take a look at it? I created a branch with the updated tailwind packages and Dialog here:
https://github.com/tremorlabs/tremor/tree/chore/updatetailwindpackagegs
PS: I recently learned, that Headless UI also exports its props, might be useful too:
Hi @severinlandolt I'll take a look at the branch and investigate the type issue. I'll do my best to address it and get things sorted out.
Hi @severinlandolt I'll take a look at the branch and investigate the type issue. I'll do my best to address it and get things sorted out.
@iamtouha Oh wow, you are quick! Thanks a ton✨ FYI: The error occurs during the build step:
Hi @severinlandolt It seems headlessui introduced a new property for dialog in their latest release. https://github.com/tailwindlabs/headlessui/pull/2709.
the fix is to add role?: "dialog" | "alertdialog";
key in DialogProps
I didn't use the DialogProp
type provided by headlessui as typescript would yell at me if I wanted to extend the type. I guess it is due to static
and unmount
dialog props.
P.S. I have no idea how can i push this change to the branch. Should I create another PR?
@iamtouha Cool! One moment, I will add you as contributor. Makes things a lot easier, have a look at your emails ;) You should now be able to directly commit to this PR 👍
@severinlandolt Cool! thanks!
Hi @severinlandolt, I apologize for any inconvenience or confusion caused by my inexperience. It seems a new PR was created whin i tried to commit to this PR as this is already closed.
Hey @iamtouha, no worries at all! I will check it right now :)
Hi @iamtouha, we just released a new version including your Dialog component! Thank you for your contribution. I was able to release your PR almost unchanged with what you submitted.
If you would like to contribute in the future, we have two issues which we would love to get some help:
loading
prop is set to true/false
. Would be great to have this replaced with something like react-transition-state would make senseThanks @severinlandolt. Excited that the Dialog component is part of the new release. It was my pleasure contributing and I'm definitely interested in contributing further. I'll take a look at these issues and see how I can assist.
Description
This PR introduces-
Dialog
andDialogPanel
componentDialog
Dialog
Related issue(s) refs #830
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
How has this been tested?
Dialog
Screenshots (if appropriate):
The PR fulfils these requirements:
main
branch