avoid-unnecessary-type-params

Unnecessary type parameters clutter code and degrade type inference. Removing generics that appear only once improves readability, simplifies maintenance, and reduces confusion during TypeScript code reviews.

Check if a generic type parameter appears only once in a function, type, or class signature. If a parameter does not relate multiple types by appearing at least twice, it is unnecessary and should be refactored.

Refactor generics by removing single-use type parameters and relying on TypeScript's built-in type inference. Ensure remaining parameters appear at least twice to properly relate types and improve overall readability.

A generic type parameter should appear at least twice in a TypeScript signature to relate multiple types. If it appears only once, it is unnecessary and should be removed to enforce safer generics decisions.

Yes, the rule applies to TypeScript function, type, and class templates. Any generic parameter that appears only once in these structures can be safely removed to improve readability and type inference.

Removing single-use type parameters is a safe refactoring practice. It streamlines type signatures without breaking existing logic, as the parameter does not relate multiple types and TypeScript can infer the type automatically.