New rule: identify missing PropType definition

Description

const propTypes = {
    actions: {
        something: PropTypes.func.isRequired,
    }.isRequired,
};

const propTypes = {
    actions: PropTypes.shape({
        something: PropTypes.func.isRequired,
    }).isRequired,
};

Contributor guide

Tech stack

javascriptreact

Domain

toolingdeveloper experience

Issue type

feature

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-2 days

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

stale

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

clear

Prerequisites

ESLint plugin developmentAST parsingReact

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

40

Research direction

The issue requests a new ESLint rule to detect missing PropTypes.shape wrapper around nested prop definitions. The example shows a case where an object literal is directly assigned as a value to a prop instead of wrapping it with PropTypes.shape. To implement this, study the existing rules in the eslint plugin react repository, particularly those related to PropTypes validation. The new rule should parse the AST to identify PropTypes assignments and verify that nested objects are wrapped with PropTypes.shape. It should also include proper test cases and documentation.