-
Notifications
You must be signed in to change notification settings - Fork 132
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 issue on Nav component #349
Comments
Can you give little detail about this issue? You want us to add proper type for this instead of giving it type any?right? I think i can work on this issue. |
Yes, that's it. We try to avoid |
Yes, it is better to remove
I start getting errors on our Item element , it means we need to check the Item element according to our types. |
@yoannfleurydev , i am stuck with this issue can you assist me what can i do ? Can you give me some pointers for this issue? |
Hey sorry for the delay, I'm a bit busy at the moment, I'm probably gonna check that this week (maybe on Friday). I let you know what I'll find. |
Hey, no worry. I explored the types little bit in depth and I got a clue. Flex is typed as According to me, this should work but it throw error
|
@Junaid300 sorry, got a lot on my plate with a huge Start UI PR and some improvements. I'm checking that tomorrow. |
I tried this solution too, but yeah, got |
If we remove |
@yoannfleurydev , any update on this ? |
Hi, no sorry, no solution at the moment on that issue. But in my head, I think about a rewrite of how we handle this part to avoid strange types. Mixing |
The text was updated successfully, but these errors were encountered: