Given that changes to the API/public method signature should be minimal to prevent breaking those client codes that use these methods, I was wondering if the Law of Demeter is less applicable to these. A simple example:class Account() {   double balance;   public void debit(Transaction t) {      balance -= t.getAmount();   }}Notice that the debit method passes the Transaction object rather than just double amount (the 'Law of Demeter', as I understand it, would say to just pass the required info, in this case just the amount, not the Transaction object...). The reason behind this, is because the method in the future might require some other Transaction properties aside from amount. From what I understand, this will prevent breaking the method signature by adding a new parameter in the future.Does this make it a sensible choice then? Or am I missing something?
Is the 'Law of Demeter' applicable to public/API method signatures?
design;api design