How to combine the factory and the law of Demeter?

Question

Programming

Good evening.
Zayuzal once again an abstract factory, and suddenly remembered that a class method should not refer to objects that any method returned. It turns out that using factories is a necessary evil, and code with factories is a priori worse than code that follows the law of Demeter? After all, even if I just return an object from the function without calling it, another class will violate this law.
If this is a matter of convenience, what is objectively better to ignore in most cases? Are factories almost an anti-pattern to be avoided to the last? And is there a solution that allows you to sit on two chairs?
Thanks in advance.

Answer 1

Zayuzal once again an abstract factory, and suddenly remembered that a class method should not refer to objects that any method returned.

The factory returns an object interface that was specifically introduced to provide generic access to the different types of objects that the factory creates. Factory users only interact with these interfaces, not with the objects themselves. That. factory users do not depend on modules that implement specific objects. The Law of Demeter is just what is needed in order to reduce the engagement between the modules. Follow the spirit of the law, not the letter.