Looser Typescript component types

[JonnyBurger]

I was in @jlengstorf's stream and I noticed that depending how you use Typescript components, you get a warning.

The following should be an acceptable way to define a React component and use it in a <Composition/> and it shouldn't trigger a warning, but still it should autosuggest types for defaultProps:

type Props = {};
export const MyComp = (props: Props) => { ... }

---

IssueHunt Summary

Backers (Total: $0.00)

Become a backer now!

Or submit a pull request to get the deposits!

Tips

• Checkout the Issuehunt explorer to discover more funded issues.
• Need some help from other developers? Add your repositories on IssueHunt to raise funds.

[issuehunt-oss]

@jonnyburger has funded $30.00 to this issue.

---

• Submit pull request via IssueHunt to receive this reward.
• Want to contribute? Chip in to this issue via IssueHunt.
• Checkout the IssueHunt Issue Explorer to see more funded issues.
• Need help from developers? Add your repository on IssueHunt to raise funds.

[issuehunt-oss]

@jonnyburger has cancelled funding for this issue.(Cancelled amount: $30.00) See it on IssueHunt