noctcore-react/max-props-per-component

A props contract wider than the cap means the component does too much.

Recommended preset: error · Autofix: no · Suggestions: no · Type information: not needed

Why

A *Props contract with many members is a strong signal that the component is doing too much — it is juggling too many independent concerns. Capping the local surface pushes you to split the component or group related props into cohesive objects. Members inherited via extends (or an intersection) are not counted, so composing a shared base contract stays free while widening the local surface does not.

What it flags

Any *Props interface or object type-literal alias that declares more than max (default 12) locally-declared members (TSPropertySignature / TSMethodSignature). The rule is layout-independent: it keys off the *Props naming convention and applies wherever the contract is declared.

Incorrect

// 13 local props
export interface BoardProps {
  p1: string;
  p2: string;
  p3: string;
  p4: string;
  p5: string;
  p6: string;
  p7: string;
  p8: string;
  p9: string;
  p10: string;
  p11: string;
  p12: string;
  p13: string;
}

Correct

// inherited members are free: only the local surface counts
export interface BoardProps extends BaseProps {
  a: string; b: string;
}

What it does not flag

• Members inherited via extends or an intersection: BaseProps with 10 members plus 12 local ones passes.
• Types not named *Props, and a *Props alias that is not an object type literal (a union or a mapped type).
• A contract at exactly max members.

Options

Option	Type	Default	Meaning
max	integer (≥1)	12	Maximum locally-declared members in a *Props contract.

'noctcore-react/max-props-per-component': ['error', { max: 12 }]

When not to use it

If your codebase does not name props types with a *Props suffix, this rule never fires — it keys off that convention.