`toBeHex` incorrectly handles zero case

[die-herdplatte]

Ethers Version

6.15.0

Search Terms

utils, math, toBeHex

Describe the Problem

A call to toBeHex with value and width set to zero throws although it should return 0x.

Code Snippet

toBeHex(0, 0)

Contract ABI

Errors

RangeError: value exceeds width (0 bytes) (operation="toBeHex", fault="overflow", value=0, code=NUMERIC_FAULT, version=6.15.0)

Environment

No response

Environment (Other)

No response

[ricmoo]

I’ve been mulling this over since you opened the issue and have come to the conclusion I agree. :)

It seems like a singularity of sorts, but the dual converting an empty Uint8Array to a number would return 0, so I like the symmetry.

It will be in the next minor bump (since it is changing behaviour).

Thanks!

[ricmoo]

One quick note regarding this change. The behaviour seems slightly inconsistent when toBeHex(0) is used, since it will return "0x00".

In a future version, that should also probably return "0x".

[ricmoo]

Fixed in v6.16.0. Thanks! :)