Handling errors not as Any

[gagiuntoli]

Describe the Feature

I would like to know if this TODO that refers to returning an error as any is going to be solved soon. I saw in the v6-beta-exports that this was fixed, am I right?

Code Example

No response

[ricmoo]

In v6, you can use the isError function. For example, catch(error:any) { if (isError(error, "UNSUPPORTED_OPERATION") { … } }, and inside that if block, all properties are asserted to exist and be defined according to the ErrorCode description. :)

[ricmoo]

The v6-beta-exports is v6. :)

I’m hoping to have the first RC ready by December.

[gagiuntoli]

And is there a way to do something like catch(error: ErrorType), I mean to avoid using any?

[ricmoo]

You can use unknown too, but I believe typescript only allows the type of a catch to be either unknown or any, but the isError can up-cast or down-cast it (respectively) to the EthersError type.

[ricmoo]

For more info, see this article.

[KholdStare]

Just wanted to say error is T is an awesome typescript feature I wasn't aware of. That's a perfect usecase for it 👍