-
Notifications
You must be signed in to change notification settings - Fork 47
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
<DropdownMenu.Content> type error #98
Comments
One possible thing can solve this may be change the code like this: export type MenuContentProps = {
children: React.ReactNode
style?: ViewStyle
-- } & Pick<
++ } & Partial<Pick<
RadixContentProps,
| 'loop'
| 'side'
| 'align'
| 'alignOffset'
| 'avoidCollisions'
| 'collisionPadding'
| 'sideOffset'
-- >
++ >> the original code can be found in this link Additionally, the problem also shows in Before the author confirm this, we can also ignore the type error by add comment |
Sorry I missed this earlier. This actually indicates that for some reason the radix types aren’t being pulled into your app. Are you using yarn or NPM? The partial workaround will work, but only because it’s doing I’m using yarn and not seeing this issue myself. Which version of zeego are you on? Thanks! |
If you are using NPM, does adding —legacy-peer-deps to your install script help? |
i get the error and i use |
seeing the same using pnpm |
you could try installing |
I'm using bun, and this does not fix it unfortunately. I did notice there were three problematic props that, when removed from the Content type in
Just found this library so couldn't find where those typescript files come from, but hope this helps. |
Just want to confirm that for both |
Is this on v2 as well? Can you use —legacy-peer-deps when you run install? I think this is an issue with npm/pnpm potentially |
Can confirmed this is introduced by v2. v2 is unuseable until this is fixed |
Yeah, I only started seeing the errors after upping to v2. |
Same issue using yarn |
Working on a fix |
Fixed in |
In version |
Just published 2.0.4 which I think would fix this |
Awesome, thanks! |
I'm using
Same issue with
|
I’ll check tomorrow, should be a simple fix. New versions of TS have perf improvements but result in issues for putting imported types in generics |
|
I have the same issue (i think), but on DropdownMenu.Label:
|
this issue was fixed for me by upgrading to 2.0.4 |
Still facing this issue after upgrading to 2.0.4
Besides that, action |
Looks like if you have If only the main |
Is it possible to fix this type error from showing up on all <DropdownMenu.Content> tags? While the app app still works with the error, its making things a bit painful as most of my files have an error showing.
The text was updated successfully, but these errors were encountered: