Why is this an issue?

A class that grows too much tends to aggregate too many responsibilities and inevitably becomes harder to understand and therefore to maintain. Above a specific threshold, it is strongly advised to refactor the class into smaller ones which focus on well defined topics.

Exceptions

The Rule ignores Classes that have:

• Only getter and setter functions
• An @Entity annotation implying that the class is an entity of a database