prop-types-exact
For use with React PropTypes. Will error on any prop not explicitly specified.
by ljharbJavaScript
Commit activity
Last 12 weeks · 0 commits
Community health
4 of 6 standards met
Recent fixes
I'm surprised if no one else has reported this, so perhaps I'm doing something odd, but I am getting the warning on several React components that are used in lists. The prop is, of course, required when components are used in a list, and used to be fine with this, but recently starting displaying the warning. From what I can tell, the issue is caused by the change from using to using in this commit: https://github.com/ljharb/prop-types-exact/commit/5a182fdc26b630fd20a917c35aefa249b20bacfb#diff-bfe9874d239014961b1ae4e89875a6155667db834a410aaaa2ebe3cf89820556R40 My guess it that React must mark the prop as non-enumerable, so didn't return it but does.
Just recently getting this error on all our builds . Using 2.16.0 so we can't downgrade to 1.2.0 as it's not a direct dependency
Fixes #1. Most of these changes are copied straight from airbnb/prop-types, so let me know if there's any extra changes that need making. I also fixed some lint errors on the tests in this PR, should I pull those out into a separate one instead?
Repository: ljharb/prop-types-exact. Description: For use with React PropTypes. Will error on any prop not explicitly specified. Stars: 237, Forks: 7. Primary language: JavaScript. Languages: JavaScript (100%). License: MIT. Open PRs: 0, open issues: 1. Last activity: 5mo ago. Community health: 85%. Top contributors: ljharb, jackwilsdon.