You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit appears to be what introduced the problem: 763382f. Perhaps an alternative approach to solving that problem could be using how the types are referenced in the code - as the first argument to a stateless component, or passed in as a type parameter to React.Component for stateful ones, rather than based on a naming convention
In v6.0.0, this code was fine:
typeMyComponentProps={a: number,b: string,};functionMyComponent({ a, b }: MyComponentProps){return<div/>;}
In v6.1.0, that gives 'a' is missing in props validation and 'b' is missing in props validation. If I change the code to
typeProps={a: number,b: string,};functionMyComponent({ a, b }: Props){return<div/>;}
everything works fine.
Thanks for your great work on this project! :)
The text was updated successfully, but these errors were encountered:
This commit appears to be what introduced the problem: 763382f. Perhaps an alternative approach to solving that problem could be using how the types are referenced in the code - as the first argument to a stateless component, or passed in as a type parameter to React.Component for stateful ones, rather than based on a naming convention
In v6.0.0, this code was fine:
In v6.1.0, that gives
'a' is missing in props validation
and'b' is missing in props validation
. If I change the code toeverything works fine.
Thanks for your great work on this project! :)
The text was updated successfully, but these errors were encountered: