law-of-demeter

To fix deep object coupling, you must limit objects to interacting only with their immediate collaborators. Enforcing this principle during code reviews detects deep call chains and suggests refactoring them into simpler, decoupled interfaces.

The Law of Demeter is an object-oriented design principle dictating that a function should only talk to itself, its parameters, created objects, or global services. You should apply it during feature development and refactoring to prevent feature envy and reduce module breakage.

You can enforce object-oriented design principles during PR reviews by applying a code-review checklist that flags chained calls crossing object boundaries. This process identifies feature envy risks and proposes compliant alternatives to improve code clarity.

Yes, the Law of Demeter applies to architectural boundaries by requiring you to wrap external APIs at system edges. This limits object coupling across different layers and modules, ensuring components communicate only through direct, compliant interfaces.

The best way to refactor code violating object coupling limits is to identify where call chains cross object boundaries and wrap those external interactions. This shifts dependencies to immediate collaborators, yielding simpler interfaces and improved code clarity.