ethers: bytes argument generating the wrong type

great project and works quite well with ethers v4

however, for a function declaration like function safeTransferFrom(address _from, address _to, uint256 _id, uint256 _amount, bytes _data) typechain for ethers generates the following declaration:

    safeTransferFrom(
      _from: string,
      _to: string,
      _id: number | string,
      _amount: number | string,
      _data: (string)[]
    ): Promise<ContractTransaction>;

the _data: (string)[] argument is wrong, and should be: _data: Uint8Array

[ricmoo]

I haven’t pushed it yet, because it does support tuples yet. Should I push it now and worry about tuples later?

[quezak]

Any update on this? BTW: the culprit here looks to be in parsing the evm types – bytes actually gets interpreted as bytes1[], hence in ethers output it’s mapped to string[]. Isn’t this interpretation wrong in the first place? IMHO bytes should be interpreted as a separate EvmType and mapped to Buffer | Uint8Array or something.

    case "bytes":
return new ArrayType(new BytesType(1));