Implement more HasTezosClient methods for MorleyOnlyRpcM
Clarification and motivation
instance HasTezosClient MorleyOnlyRpcM
implements only signBytes
and only for AddressResolved
. A few methods just do nothing. Other methods just throw exceptions. We can support more methods if deemed necessary:
- We can keep track of aliases by storing them in a
Map
for example (they won't be persistent of course). -
waitForOperation
can be implemented using RPC. In this case I think it should be extended and take an argument that specifies for how many confirmations to wait (by passing 0 one can have the current behavior). -
calcTransferFee
andcalcOriginationFee
– perhaps can be implemented somehow. Though I heard that fee calculation will be added to RPC one day, so hopefully these methods will be removed fromHasTezosClient
eventually.
P. S. #651 (closed) may help as it will decrease the number of methods to consider.
Acceptance criteria
More methods in instance HasTezosClient MorleyOnlyRpcM
do something other than pass
or throwM
.
I don't specify exact methods because I think we should find a use case for these additions first, maybe nobody will ever need it.