Open daniel-savu opened 11 months ago
@daniel-savu still relevant I assume?
It is yes. We've already started consolidating environment-specific errors into ChainCommunicationError
using the From
trait impl approach (example here for cosmos), but it's a work in progress and many errors are still standalone.
I'd like to have one error enum that includes
ChainCommunicationError
,HyperlaneCustomErrorWrapper
, eyre errors, and so on. Wondering what the reasoning behind not doing this before was? cc @tkporterSome work on this has already started in https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/2881
Useful subtasks:
From<Err> for ChainCommunicationError
for all the sub-errors ofHyperlaneCosmosError
et al