-
Notifications
You must be signed in to change notification settings - Fork 109
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
created TypeScript typings #131
Comments
Hi, we use the types from definitly typed. We didn't run in any trouble with them. @types/react-measue Have you seen these? Cheers, |
Hi @thomaskempel! TBH I've assumed that a project of such size would have them included without really checking 🤦♂️ @types/react-measure probably won't work for components with default props (which I use a lot, but that's quite easily fixable). Will check if I can remove mine and patch those. Thanks! Any plans on including TypeScript typings with react-measure? |
@tkryskiewicz thanks for filing an issue! Apologies for taking a little bit to get back to you. I'm not too familiar with TypeScript yet, would this just be an additional file to include in the build? Or is DefinitelyTyped more of the way to go? |
@souporserious It's an Generally it's better for packages to include TS typings. It's much easier to test and maintain them, no need to install a Will try to put something together this week. |
Hi, while working on one of my projects I've added TypeScript typings for
react-measure
. Please check mostly if naming looks good.From what I've tested, those work:
Measure
component,withContentRect()
with class components (also with default props) and functional components.What needs to be improved:
measure()
inInjectedMeasureProps
React.Ref<any>
more preciseThe text was updated successfully, but these errors were encountered: