Instead of "the fee handler" we should be able to define several fee handlers that each focus on different things and can later be composed together with a tuple similar to how other Substrate traits allow composition.
Changing the FeeHandler trait to receive a mutable Fees object would make it easier for implementers.
Instead of "the fee handler" we should be able to define several fee handlers that each focus on different things and can later be composed together with a tuple similar to how other Substrate traits allow composition.
Changing the
FeeHandler
trait to receive a mutableFees
object would make it easier for implementers.