Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
No typings for input properties
See original GitHub issueA number of properties on the Input component do not have any typings around them and thus no type safety when developing in TypeScript.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
What does "Type A has no properties in common with type B ...
Type 'A' has no properties in common with type 'B'. This is a simplified example; your typings file is certainly more complex but...
Read more ><input>: The Input (Form Input) element - HTML
The <input> HTML element is used to create interactive controls for ... A few additional non-standard attributes are listed following the ...
Read more >Documentation - Advanced Types - TypeScript
This page lists some of the more advanced ways in which you can model types, it works in tandem with the Utility Types...
Read more >Property 'blur' does not exist on type 'Element'. · Issue #339 ...
The problem here is that page.$eval doesn't know that your selector input[id=email] will return an HTMLInputElement , but you do.
Read more >Forms and Events - React TypeScript Cheatsheets
If performance is not an issue (and it usually isn't!), inlining handlers is easiest as you can just use type inference and contextual...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@Jameskmonger your position has the right to life. However, personally I want left all as is. Possible @levithomason has another opinion at this question
Thanks for the responses @levithomason and @layershifter - I believe that with TypeScript I can actually merge the interfaces so locally I can have my own type information for the native DOM properties, so it isn’t an issue for me. Just something to consider about the wider community.