react/prop-types is missing in props validation on destructured prop types

I just recently upgraded to the latest version and started to see this. My component has proptypes that include

/** A notification to queue up for display. */
 notification: PropTypes.shape({...NotificationPropTypes}),

NotificationPropTypes are:

import PropTypes from 'prop-types';

export default {
    /** Additional class(es) to add to the component. */
    className: PropTypes.string,
    /** A unique ID to identify the notification with. The suggested way to create this is to use <a href="https://www.npmjs.com/package/uuid#quickstart---commonjs-recommended" target="_blank">uuid</a>. */
    id: PropTypes.string.isRequired,
    /** The message body of the notification. */
    message: PropTypes.node.isRequired,
    /** Determines the characteristics of the notification. */
    type: PropTypes.oneOf(['info', 'success', 'error', 'warning']),
    /** Whether to display the close button. */
    showClose: PropTypes.bool,
    /** The time (in milliseconds) that the notification stays open for. */
    duration: PropTypes.number,
    /** Whether the notification should close itself without having to click the close button after the specified duration. */
    autoClose: PropTypes.bool,
    /** A function to execute after the notification has been hidden. Will receive the notification's props. */
    onHidden: PropTypes.func
};

Offending code:

} else if (notification && !find(this._notificationQueue, {id: notification.id})) {

Its the notification.id part that its complaining about (id). Any reason why this would start to error now?

[golopot]

I am still curious though why this didn’t error in prior versions?

prop-types catches more cases since #2301.

[reintroducing]

@ljharb that’s fair, and thanks for the explanation. I’m going to close this as a non-issue then. I am still curious though why this didn’t error in prior versions? The code has been unchanged since we were probably on ESLint 2.x way back when. Were there updates made to this plugin to change that or do you think its an internal ESLint change that got smarter and started to cause this then? Appreciate the discussion as well.