Warning: getDefaultProps is only used on classic React.createClass definitions. Use a static property named `defaultProps` instead.
See original GitHub issueHi,
Warning: getDefaultProps is only used on classic React.createClass definitions. Use a static property named
defaultProps instead.
is an annoying React warning, which seems to disappear once I rebuild the project by running npm run build
or gulp clean && NODE_ENV=production gulp build
(as in package.json file).
Since contributing guidelines specifically prohibit making a PR with build files, I did not open one. However, it would be really nice to get rid of those warnings, especially given that it’s just a single build
away.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:3
- Comments:9
Top Results From Across the Web
getDefaultProps is only used on classic React.createClass ...
js:68 Warning: getDefaultProps is only used on classic React.createClass definitions. Use a static property named defaultProps instead. Here is ...
Read more >React component method only supported in createReactClass ...
React Warning: getDefaultProps is only used on classic React.createClass definitions. Use a static property named defaultProps instead.
Read more >getDefaultProps is only used on classic React.createClass ...
blueocean.js:7383 Warning: getDefaultProps is only used on classic React.createClass definitions. Use a static property named `defaultProps` instead.
Read more >DefinitelyTyped/DefinitelyTyped - Gitter
Warning : getDefaultProps is only used on classic React.createClass definitions. Use a static property named defaultProps instead.
Read more >[BIR-19] getDefaultProps is only used on classic React ...
getDefaultProps is only used on classic React.createClass definitions. Use a static property named `defaultProps` instead.
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
@agirton The warning is also being displayed in here. Any ETA for the fix?
@agirton, is there any word on when a release will be made that will fix this?