[React 16.2] Warning: Component Menu declared `PropTypes` instead of `propTypes`. Did you misspell the property assignment?
See original GitHub issueVersion
2.0.1
Steps to reproduce
- Install React 16.2, as it only repros with the latest version.
- In Chrome (or probably any other browser), open the dev console.
- Take any Typeahead instance you might have, and type enough characters to show the menu.
Expected Behavior
- No warnings/errors.
Actual Behavior
As soon as the menu pops up, React shows the following:
Warning: Component Menu declared ``PropTypes`` instead of ``propTypes``. Did you misspell the property assignment?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:4
- Comments:11 (3 by maintainers)
Top Results From Across the Web
Component [ComponentName] declared `PropTypes` instead ...
Error : Component [ComponentName] declared `PropTypes` instead of `propTypes`. Did you misspell the property assignment? Ask Question. Asked 1 ...
Read more >Don't Call PropTypes Warning - React
bool . This pattern by itself is fine, but triggers a false positive because React thinks you are calling PropTypes directly. The next...
Read more >Upgrade ReactJS.NET 5.0.0 and React 16.8 for the ASP.NET ...
Warning : Component popover declared `PropTypes` instead of `propTypes`. Did you misspell the property assignment? The solution is to replace PropTypes with ...
Read more >How to validate React props using PropTypes - LogRocket Blog
We can use React props, short for properties, to send data from one component to another. If a component receives the wrong type...
Read more >prop-types - npm
You can use prop-types to document the intended types of properties passed to components. React (and potentially other libraries—see the ...
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 FreeTop 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
Top GitHub Comments
@ToJen The error you’re seeing might be because you did something like
the first
PropTypes
is supposed to be a small letter. It should beLooks like this issue still exists:
Warning: Component FieldWrapper declared ``PropTypes`` instead of ``propTypes``. Did you misspell the property assignment?