Skip to content
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

'anchor' does not exist in Tooltip #1030

Closed
huynhtastic opened this issue Apr 15, 2020 · 8 comments · Fixed by #1055
Closed

'anchor' does not exist in Tooltip #1030

huynhtastic opened this issue Apr 15, 2020 · 8 comments · Fixed by #1055
Labels
🐛 Bug 📱 Components components module-specific

Comments

@huynhtastic
Copy link

🐛 Bug Report

Typescript reports that the anchor prop does not exist on Tooltip.

To Reproduce

Steps to reproduce the behavior:

Expected behavior

For anchor to be a correct prop for Tooltip.

Link to runnable example or repository (highly encouraged)

image

UI Kitten and Eva version

Package Version
@eva-design/eva 5.0.0-alpha.1
@ui-kitten/components 5.0.0-alpha.1
@artyorsh
Copy link
Collaborator

Agreed. There’re lots of ts issues I realized myself in a real-world application. Will be solved in alpha.2 Thanks for reporting 👍

@huynhtastic
Copy link
Author

I've run into a few other missing props for some other components as well. Would you like me to list those as well?

@artyorsh
Copy link
Collaborator

Sure. That’s would be a great help

@huynhtastic
Copy link
Author

I was looking through my codebase, but the only one I could find again so far was that Popover is missing backdropStyle.

I can comment on this issue as I find more. Thanks for the help!

@artyorsh
Copy link
Collaborator

@huynhtastic installing utility-types solves most of the cases. You should install it as devDependency to solve this issue temporary.

The reason is that in v5 we moved to this library instead of defining common types ourselves.

@huynhtastic
Copy link
Author

Ok great! Thanks for the heads up.

Is that in the documentation somewhere? I don't remember reading anything about installing utility-types as a dependency.

@artyorsh
Copy link
Collaborator

No it’s not. It seems I missed to notice that and now I’m thinking whether it’s ok for users to install this lib if we describe it or we should move back to own type system

@huynhtastic
Copy link
Author

I think for now, it'd be best if you included it in your documentation so other won't run into this problem as long as you are still using utility-types.

@artyorsh artyorsh mentioned this issue Apr 26, 2020
2 tasks
@artyorsh artyorsh linked a pull request Apr 26, 2020 that will close this issue
2 tasks
@artyorsh artyorsh added 🐛 Bug 📱 Components components module-specific labels Apr 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Bug 📱 Components components module-specific
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants