-
Notifications
You must be signed in to change notification settings - Fork 1.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
Type error on Switch #240
Comments
Hey! Thank you for your bug report! Is this only happening while using |
Hello, here's a reproduction: https://github.com/targos/headlessui-switch-bug |
@targos thanks for the repro! I'll take a look now! |
Thanks @targos :) |
Ideally we can use a Symbol, however it seems that TypeScript or TSDX, inlines the `unique symbol`, instead of referencing the actual __ placeholder type. Ideally we add this back in the future, but the odds that somebody has this specific uuid in production is close to 0. (Unless they specifically use this uuid). Fixes: #240 Thanks to =?UTF-8?q?Micha=C3=ABl=20Zasso?= <[email protected]> for providing a reproduction repository!
* replace unique symbol with uuid v4 Ideally we can use a Symbol, however it seems that TypeScript or TSDX, inlines the `unique symbol`, instead of referencing the actual __ placeholder type. Ideally we add this back in the future, but the odds that somebody has this specific uuid in production is close to 0. (Unless they specifically use this uuid). Fixes: #240 Thanks to =?UTF-8?q?Micha=C3=ABl=20Zasso?= <[email protected]> for providing a reproduction repository! * update changelog
This should be fixed, and will be available in the next release. |
i will try that thanks :) |
Thanks @RobinMalfait Do you consider to release a patch to have a clean fix before the next version is released? Or should we install an older version of headlessui ? |
* replace unique symbol with uuid v4 Ideally we can use a Symbol, however it seems that TypeScript or TSDX, inlines the `unique symbol`, instead of referencing the actual __ placeholder type. Ideally we add this back in the future, but the odds that somebody has this specific uuid in production is close to 0. (Unless they specifically use this uuid). Fixes: #240 Thanks to =?UTF-8?q?Micha=C3=ABl=20Zasso?= <[email protected]> for providing a reproduction repository! * update changelog
* replace unique symbol with uuid v4 Ideally we can use a Symbol, however it seems that TypeScript or TSDX, inlines the `unique symbol`, instead of referencing the actual __ placeholder type. Ideally we add this back in the future, but the odds that somebody has this specific uuid in production is close to 0. (Unless they specifically use this uuid). Fixes: #240 Thanks to =?UTF-8?q?Micha=C3=ABl=20Zasso?= <[email protected]> for providing a reproduction repository! * update changelog
* replace unique symbol with uuid v4 Ideally we can use a Symbol, however it seems that TypeScript or TSDX, inlines the `unique symbol`, instead of referencing the actual __ placeholder type. Ideally we add this back in the future, but the odds that somebody has this specific uuid in production is close to 0. (Unless they specifically use this uuid). Fixes: #240 Thanks to =?UTF-8?q?Micha=C3=ABl=20Zasso?= <[email protected]> for providing a reproduction repository! * update changelog
* replace unique symbol with uuid v4 Ideally we can use a Symbol, however it seems that TypeScript or TSDX, inlines the `unique symbol`, instead of referencing the actual __ placeholder type. Ideally we add this back in the future, but the odds that somebody has this specific uuid in production is close to 0. (Unless they specifically use this uuid). Fixes: #240 Thanks to =?UTF-8?q?Micha=C3=ABl=20Zasso?= <[email protected]> for providing a reproduction repository! * update changelog
Hello 👋
I'm using the @headlessui/react in 0.3.1 package with typescript 4.1.5
And when i'm trying to use the application with "tsc --noEmit" i have the following error:
This is the output in my node_modules ...
i can help you if you have any questions
Have a nice day :) 👋
The text was updated successfully, but these errors were encountered: