Use LogDeferred
to handle errors when closing iteration
#2846
Labels
type: code hygiene
Clean up code but without changing functionality or interfaces
type: refactor
Architecture, code or CI improvements that may or may not tackle technical debt.
Milestone
Summary
Currently we ignore any errors returned by
iterator.Close()
, once we update to SDK v0.47, we should utilize the newly added cosmos/cosmos-sdk#11785LogDeferred
function. I think it is fine to do all theLogDeferred
additions in a single pr as the changes should be straight forward.This change might require a version > v0.47 (I haven't checked what release the function will be in)
For Admin Use
The text was updated successfully, but these errors were encountered: