Unexpected data returned when decoding input with a tuple[] type about ethereum-input-data-decoder HOT 3 CLOSED

Hey @miguelmota, what's the intended return value for an input with tuples in it?

I think I've figured out the decoding issue for tuple and tupe[], just need to tidy up what's returned.

mostly unsure about how to structure names.

where OrderData is

struct OrderData {
  uint256 amount;
  address buyer;
}

what do you think about this?

for a method sig someMethod(address,OrderData)

{
  method: 'someMethod',
  types: ['address', '(uint256,address)'],
  inputs: [
    '0x81c55017F7Ce6E72451cEd49FF7bAB1e3DF64d0C',
    [100, '0xA37dE6790861B5541b0dAa7d0C0e651F44c6f4D9']
  ],
  names: ['sender', ['order', ['amount', 'buyer']]]
}

for a method sig someMethod2(address,OrderData[])

{
  method: 'someMethod2',
  types: ['address', '(uint256,address)[]'],
  inputs: [
    '0x81c55017F7Ce6E72451cEd49FF7bAB1e3DF64d0C',
    [[100, '0xA37dE6790861B5541b0dAa7d0C0e651F44c6f4D9']]
  ],
  names: ['sender', ['allOrders', ['amount', 'buyer']]]
}

from ethereum-input-data-decoder.

just an FYI @miguelmota so we don't duplicate work, I'll be spending some time debugging this today and tomorrow. will let you know how I go.

from ethereum-input-data-decoder.

@liamaharon the nested array structure is great 👍

from ethereum-input-data-decoder.