We're using "Component.PropTypes" (with uppercase P) instead of Component.propTypes (lowercase p) in around 16 places in the whole codebase. I guess the typo was introduced in one component and has been copy-pasted multiple times.
Using PropTypes doesn't actually detect the problems. For example, skillsCategory can be undefined in TalentPickerQuestion component. But it's marked as required. We're supposed to get an error in such a scenario according to prop types. But We'll not see the error message as we're using PropTypes.
We have such issues in Connect App and in react-components repositories
Reported by Vigneshkumar:
We're using "Component.PropTypes" (with uppercase P) instead of Component.propTypes (lowercase p) in around 16 places in the whole codebase. I guess the typo was introduced in one component and has been copy-pasted multiple times.
Using PropTypes doesn't actually detect the problems. For example, skillsCategory can be undefined in TalentPickerQuestion component. But it's marked as required. We're supposed to get an error in such a scenario according to prop types. But We'll not see the error message as we're using PropTypes.
We have such issues in Connect App and in react-components repositories