law-of-demeter

The Law of Demeter is a design guideline for object-oriented programming that restricts object interactions, ensuring a method only talks to immediate friends rather than deeply nested objects, promoting loose coupling and maintainability.

To refactor a train wreck anti-pattern, you should transform chained calls like `a.getB().getC().doX()` into direct interactions by introducing delegated methods on the immediate object, reducing excessive coupling.

Yes, this refactoring guidance supports multiple languages including Python, Go, Java, Kotlin, Scala, TypeScript, Ruby, and Rust to detect and eliminate train wreck patterns across diverse object-oriented codebases.

To detect Law of Demeter violations during code review, look for methods making many chained calls to access deeply nested data, which indicates a train wreck pattern that requires refactoring into delegated methods.

You should avoid strictly applying the Law of Demeter when dealing with data transfer objects, fluent interfaces, or method chaining in functional pipelines, as enforcing it in these contexts can create unnecessary wrapper methods and reduce readability.